Python and Autoconf

Martin von Loewis loewis at
Sun May 27 07:39:49 EDT 2001

Glen Starchman <glen at> 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 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 build", instead of invoking the C compiler


More information about the Python-list mailing list