This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients eric.araujo, ezio.melotti, pitrou
Date 2011-11-26.14:26:30
SpamBayes Score 6.27276e-15
Marked as misclassified No
Message-id <1322317591.03.0.28482488503.issue13472@psf.upfronthosting.co.za>
In-reply-to
Content
> I have a few arguments in favor of my position:
Hm, I said that people wanted a “feature-full library” but I was confused: We’re talking about a Python built for contributing, not to develop your app, so my argument does not apply.  So, the devguide should list the optional build deps *and* say something like “these are not needed to run Python and its test suite, but you may need one them of for some patches”.

> (I've found and fixed several issues related to zlib because it was missing here)
I know :)  I have a Python built without threads and run packaging and distutils tests with it from time to time, but it seems I can’t disable zlib at configure time.

>> the addition of this message and further edits to its wording were done
>> exactly to avoid people worrying that their python binary is not usable.
> But it's still missing an "optional" before modules imho.
What I meant is that the history of this messages says that you can just go ahead and add “optional”.

> The second message that says to "look in setup.py in detect_modules()" doesn't seem too
> useful too (but maybe I should take a look ;).
It is scary code.

>> Okay; do we need to collect info for all major OSes
> You can also do it incrementally
Okay, I’ll make a patch.
History
Date User Action Args
2011-11-26 14:26:31eric.araujosetrecipients: + eric.araujo, pitrou, ezio.melotti
2011-11-26 14:26:31eric.araujosetmessageid: <1322317591.03.0.28482488503.issue13472@psf.upfronthosting.co.za>
2011-11-26 14:26:30eric.araujolinkissue13472 messages
2011-11-26 14:26:30eric.araujocreate