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 xdegaye
Recipients Alex.Willmer, akuchling, bennykj, doko, martin.panter, xdegaye, yan12125, zach.ware
Date 2016-10-27.10:27:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477564031.44.0.624585611887.issue28444@psf.upfronthosting.co.za>
In-reply-to
Content
New patch taking into account Martin last review and some updated comments.

>> Why do you remove the code that loops over Modules/Setup? Maybe is it redundant with the other code for removing the already-built-in modules?
> Yes because this is redundant, maybe not the case when this was written 15 years ago.

* sys.builtin_module_names are the modules listed in the _PyImport_Inittab[] array that is built by Modules/makesetup from Modules/config.c.in and the '*static*' modules configured in the Setup files (those Setup files that are listed in the rule of the 'Makefile' target of the Makefile).  This list is missing the '*shared*' modules configured in the Setup files and that should not be built by setup.py.
* The setup.py code that loops over and loosely parses some of the Modules/Setup files, excludes both '*static*' and '*shared*' modules from the built modules.
* 'MODNAMES' does the same thing in the patch accurately as the list is built by makesetup.

New issue 28542 to document the cross-compilation.
History
Date User Action Args
2016-10-27 10:27:11xdegayesetrecipients: + xdegaye, akuchling, doko, martin.panter, zach.ware, Alex.Willmer, yan12125, bennykj
2016-10-27 10:27:11xdegayesetmessageid: <1477564031.44.0.624585611887.issue28444@psf.upfronthosting.co.za>
2016-10-27 10:27:11xdegayelinkissue28444 messages
2016-10-27 10:27:11xdegayecreate