Zack> I'm piggybacking on this thread to point out that there are some Zack> pretty drastic simplifications possible in configure.in. To paraphrase Tim, Guido, MvL and many others: "Patches are welcome". You knew that would be the canned reply, right? <wink> The Python configure script has been around for a long time. I suspect much of the cruft that's there is simply because it hasn't kept up with newer versions of autoconf. The sizeof check for the char type probably predates the decision to require an ANSI C compiler. I can probably elide that without breaking too much. Zack> Another cleanup that would be nice is to get rid of Modules/Setup Zack> and related; as I understand it, this is only around because the Zack> top level setup.py hasn't been finished yet. (And for a pipe Zack> dream, could we have a way to set the disabled_module_list from Zack> the configure command line?) Nothing's really ever finished, least of all distutils... I believe Modules/Setup is still the best (only?) way to create a statically linked interpreter (all extension modules builtin) or add your own extension modules without fiddling setup.py. Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4