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 tarek
Recipients Arfrever, ahonkela, brian.curtin, christian.heimes, drkirkby, mdboom, tarek
Date 2010-03-10.20:40:26
SpamBayes Score 1.5203343e-08
Marked as misclassified No
Message-id <1268253628.91.0.467880064657.issue1222585@psf.upfronthosting.co.za>
In-reply-to
Content
If we consider that Distutils didn't provide c++ support, and that it partially worked by accident (through gcc), I would call it a new feature. Especially since it requires a new option.

We are freezing the API so we can't add options to methods/functions. 

That's why it could be done on distutils2 instead, which will be released when 2.7 final is released (but not in the stdlib), and backward compatible with 2.4, 2.5, 2.6.

If we could do the proper job for C++ support in distutils2 that would be better. 

Notice that distutils2 is a fork of how distutils was in trunk last month, so it should be fairly simple to depend on it in your project, to benefit from new features etc. The goal is to push it back in the stdlib in 3.3. 

If you want to start a dev. branch of your project using distutils2, I am willing to help there.
History
Date User Action Args
2010-03-10 20:40:29tareksetrecipients: + tarek, mdboom, christian.heimes, ahonkela, Arfrever, brian.curtin, drkirkby
2010-03-10 20:40:28tareksetmessageid: <1268253628.91.0.467880064657.issue1222585@psf.upfronthosting.co.za>
2010-03-10 20:40:27tareklinkissue1222585 messages
2010-03-10 20:40:26tarekcreate