Patches item #1673619, was opened at 2007-03-04 22:31 Message generated for change (Comment added) made by loewis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1673619&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Distutils and setup.py Group: Python 2.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Skip Montanaro (montanaro) Assigned to: Nobody/Anonymous (nobody) Summary: Identify modules to be built and not built Initial Comment: A user has been moaning on c.l.py that Python's setup.py doesn't bail out when the necessary bits can't be found to build a particular extension module (curses in this case). For reasons that should be obvious to this crowd you simply can't have it stop if a particular module can't be built. This patch is a compromise. It enumerates the modules for which the necessary build mojo exists and those modules for which it doesn't. I'm personally a bit ambivalent about it, both the need for it and my particular implementation. An alternate implementation might create a set of all module names at the start of the run then subtract the modules which could be built from that. This implementation has the slight advantage that all the fiddling for a particular module occurs near the tests for that module. Skip ---------------------------------------------------------------------- >Comment By: Martin v. Löwis (loewis) Date: 2007-03-05 10:18 Message: Logged In: YES user_id=21627 Originator: NO I don't think the modules that it builds successfully need to be printed - the build messages will tell, anyway. I'm not sure when it prints these things. IMO, they should be printed at the end of the build (i.e. after all modules have been built). It should also print out, in summary, modules that had been attempted to build, but where building failed for some reason. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1673619&group_id=5470 _______________________________________________ Patches mailing list [email protected] http://mail.python.org/mailman/listinfo/patches
