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, jkloth, josip, l0nwlf, meatballhat, pitrou, schmir, tarek, titus, zubin71
Date 2010-07-17.21:09:22
SpamBayes Score 0.00779759
Marked as misclassified No
Message-id <>
Tarek also answered my questions.

1) 4) build and install options should be defined and checked only once, in configure. build and install would inherit from this class and get their option from it.

3) I switched to using distutils2.core.run_setup, which Tarek said is okayish. Understanding why the usual idiom of using the classes directly doesn’t work will be better.

5) Since the cache file (the file that contains options, written by configure) is tied to a precise build, it should be specific. I can put the platform and Python version in the filename, or maybe put the file in the platform-specific build directory. Not sure about the naming in dists. I still have to think about the overlap between setup.cfg and configure.cache.
Date User Action Args
2010-07-17 21:09:24eric.araujosetrecipients: + eric.araujo, titus, pitrou, schmir, tarek, jkloth, meatballhat, zubin71, l0nwlf, josip
2010-07-17 21:09:24eric.araujosetmessageid: <>
2010-07-17 21:09:23eric.araujolinkissue8254 messages
2010-07-17 21:09:22eric.araujocreate