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 doko
Recipients doko, eric.araujo, koobs, pitrou, thomas-petazzoni, vstinner
Date 2014-03-25.08:14:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> But this expectation is not true: if dependencies are not available,
 > Python silently disables the build of certain modules. So this story
> of making the standard library always has all the modules does not really stand.

I think this one is a valid concern. Did run into it myself, because a final 
package was built on another kernel and disabled some semaphore stuff by accident.

None of the extensions above are built as builtins by default, so you can always 
prune these after the build.  What I think is needed is a mode which breaks the 
build when some extensions are not built. Whether this should be the default or 
not, ... but it would give you a chance for a deterministic build.  And the 
build system already tells you at the end of the extension builds that some 
extensions didn't build which were expected to build.
Date User Action Args
2014-03-25 08:14:11dokosetrecipients: + doko, pitrou, vstinner, eric.araujo, koobs, thomas-petazzoni
2014-03-25 08:14:11dokolinkissue20210 messages
2014-03-25 08:14:10dokocreate