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 BreamoreBoy, LRN, Ray.Donnelly, WhiteTiger, alesko, amaury.forgeotdarc, davidfraser, eric.araujo, giampaolo.rodola, kalev, lkcl, rpetrov, rschoon.old, schmir, scott.tsai, tarek
Date 2012-06-30.16:39:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341074396.51.0.438010868012.issue3871@psf.upfronthosting.co.za>
In-reply-to
Content
> I thought that the distutils-is-frozen rule was only for Python 2.x
> and that they would be allowed for 3.x? Is this not true?
It is not.  The normal rule is that stable versions (like 2.7) get only bug fixes while new features go only to the development version (like 3.3 before it went into beta last Tuesday).  For distutils there is a special rule that prevents new features for all versions.  The only exceptions are side effects of changes in other parts of Python (for example __pycache__ directories in 3.2 or virtualenv in 3.3).

> Obviously making Python cross compile properly is a very desired feature (in this day and age
> I'd say cross-compilation for any major software is expected to be honest with you).
Well I for one am a unix user but not a C guy; I compile Python easily and don’t fully get the benefits of cross compilation.

distutils2 is the place to add such new features.  We wanted to release it in the standard library for 3.3 but it was not ready, so it should be in 3.4.
History
Date User Action Args
2012-06-30 16:39:56eric.araujosetrecipients: + eric.araujo, lkcl, amaury.forgeotdarc, davidfraser, giampaolo.rodola, schmir, scott.tsai, tarek, rpetrov, rschoon.old, WhiteTiger, BreamoreBoy, LRN, alesko, kalev, Ray.Donnelly
2012-06-30 16:39:56eric.araujosetmessageid: <1341074396.51.0.438010868012.issue3871@psf.upfronthosting.co.za>
2012-06-30 16:39:51eric.araujolinkissue3871 messages
2012-06-30 16:39:50eric.araujocreate