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 ajaksu2, benjamin.peterson, kxroberto, tarek
Date 2009-05-13.07:55:42
SpamBayes Score 6.915506e-09
Marked as misclassified No
Message-id <1242201356.36.0.774584120962.issue5977@psf.upfronthosting.co.za>
In-reply-to
Content
new_compiler takes "compiler" as a compiler name. It would make much
sense to make it accept a compiler instance.

now for people setup.py, I wasn't aware that people are using
build_ext.compiler as a compiler, besides Python itself.

IMHO we should rename the compiler option to "compiler_type" then
provide an API build_ext.get_compiler() then fix Python setup.py file.

Then this should not go into 2.6 but in 2.7, and we should put back the
option in new_compiler like it was (it's wrong but at least it works if
you run the command just once, which is the most common case)
History
Date User Action Args
2009-05-13 07:55:56tareksetrecipients: + tarek, kxroberto, ajaksu2, benjamin.peterson
2009-05-13 07:55:56tareksetmessageid: <1242201356.36.0.774584120962.issue5977@psf.upfronthosting.co.za>
2009-05-13 07:55:54tareklinkissue5977 messages
2009-05-13 07:55:53tarekcreate