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 eli.collins
Recipients alexis, eli.collins, eric.araujo, tarek
Date 2011-06-02.15:28:42
SpamBayes Score 3.436651e-07
Marked as misclassified No
Message-id <1307028523.76.0.0549970473948.issue12242@psf.upfronthosting.co.za>
In-reply-to
Content
It would be useful to have an environment marker which matched the compiler being used when compiling a C extension. 

Sometimes different compilers require different options (different lib names, different flags, etc); distutils1 setup.py files which have to deal with this currently go through some convolutions to determine the current compiler, and then dynamically modify extra_compile_args before handing them off to setup. 

Since packaging is moving to a setup.cfg file, it would be useful to be able to use an environment marker along the lines of  'extra_compile_args = -Dmingw_specific_flag ; packaging.c_compiler == "mingw"', allowing for special options for mingw vs msvc, etc. 

Since issue 11921 made it sound like environment markers had been expanded to the extensions sections, I'm hoping this isn't too complicated (but don't know the codebase well enough to write a patch myself).
History
Date User Action Args
2011-06-02 15:28:43eli.collinssetrecipients: + eli.collins, tarek, eric.araujo, alexis
2011-06-02 15:28:43eli.collinssetmessageid: <1307028523.76.0.0549970473948.issue12242@psf.upfronthosting.co.za>
2011-06-02 15:28:43eli.collinslinkissue12242 messages
2011-06-02 15:28:42eli.collinscreate