Deploying Python _Applications_

Sridhar R sridharinfinity at yahoo.com
Tue Feb 3 16:08:28 CET 2004


miki.tebeka at zoran.com (Miki Tebeka) wrote in message news:<4f0a9fdb.0402020353.8b2ea08 at posting.google.com>...
> Hello Sridhar,
> 
> > 1. Installtion prefix contants '/usr/ or /usr/local'
> > 2. Some constants set during build (like 'HAVE_GTK2' in autoconf)
> > 
> > I searched the distutils documentation and seems to be distutils can't
> > handle these.
> > 
> > Any thoughts?
> You can write any code you like in the `setup.py' script.
> I use a .ini file with all these parameters written at install time
> (on M$ world NSIS is doing this). And then at run time the script load
> the .ini file and run.

  Do you mean I should write code (in setup.py) such that the user is
allowed to pass the prefix directory something like
./setup.py --prefix=/usr/local
  and the code should parse this install data files in
 @prefix/share/<appname>/...
  automatically.

  Well. I can do that.  But all I wanted is a _standard_ tool for
doing all these, something like distutils for python packages and
autoconf for any.  py2exe can be uses, but only in M$ Windows.
  Anything there specialised for python (like autoconf)

> HTH.
> Miki



More information about the Python-list mailing list