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 lkcl
Recipients BreamoreBoy, LRN, WhiteTiger, alesko, amaury.forgeotdarc, davidfraser, eric.araujo, giampaolo.rodola, kalev, lkcl, rpetrov, rschoon.old, schmir, scott.tsai, tarek, zooko
Date 2011-08-25.20:15:33
SpamBayes Score 0.00031887068
Marked as misclassified No
Message-id <1314303334.07.0.200199173687.issue3871@psf.upfronthosting.co.za>
In-reply-to
Content
eric,

if you recall there was some discussion that it was acceptable to use distutils but *only* for python 2.N (on the basis that its use is so well entrenched that it would be impossible to force python2.N applications to start using distutils2), and i agreed wholeheartedly with you that the expectation to use distutils2 would be reasonable for python3.N

just as an aside: have all python 3.N packaging scripts, for all python-dev scripts *and* all 3rd party packages world-wide, been using distutils2 by default instead of distutils?
History
Date User Action Args
2011-08-25 20:15:34lkclsetrecipients: + lkcl, zooko, amaury.forgeotdarc, davidfraser, giampaolo.rodola, schmir, scott.tsai, tarek, eric.araujo, rpetrov, rschoon.old, WhiteTiger, BreamoreBoy, LRN, alesko, kalev
2011-08-25 20:15:34lkclsetmessageid: <1314303334.07.0.200199173687.issue3871@psf.upfronthosting.co.za>
2011-08-25 20:15:33lkcllinkissue3871 messages
2011-08-25 20:15:33lkclcreate