Python and Autoconf

[Glen Starchman]

Martin von Loewis wrote:
> 
> Glen Starchman <glen at enabledventures.com> writes:
> 
> > The other reason I have gone with Autoconf is that it is a standard.
> > The people who I will be turning this project over to are not um,
> > technically competent. They *do* know how to run ./configure --help
> > and that's about it. I can't see them editing a setup.py script,
> > which is what they would have to do if something went wrong (eg... a
> > bad path).
> 
> I'm not suggesting that your users would compile your package in any
> different way. You'ld still have a makefile, but making all would
> invoke "python setup.py build", instead of invoking the C compiler
> directly.

Sure. There are already parts of my Makefile.in that look like:

update_files:
	@ @PYTHON@ @srcdir@ utility/change.py @somearg@

Why? Because it is much cleaner for me to write a recursive search
and replace function in Python than in awk. ;-)

And, one of the packages that I am using (MySQL-Python) uses
DistUtils, so its entry in the master makefile is simply:

MySQLdb:
	@ @PYTHON@ @MYSQLDB_DIR@/setup.py build


So, point taken. ;-)


> 
> Regards,
> Martin