➜

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 alecsandru.patrascu
Recipients alecsandru.patrascu, brett.cannon, gregory.p.smith, scoder, skip.montanaro, skrah
Date 2015-08-25.17:34:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440524096.57.0.482692079979.issue24915@psf.upfronthosting.co.za>
In-reply-to
Content 
Sorry, it was a typo. I made a correction to it. I will also modify to -m flag, instead of the explicit file execution. 

Regarding the clang/gcc support, in v03 version of patches, GCC is supported. On Linux is straightforward. On Mac I see that the default development environment also has the "gcc" command, but it is a binary stub that calls clang in backend, so the flags are adjusted for clang-in-gcc-clothing. You say to support clang explicitly as a compiler in 2.7 and 3.6?
History
Date User Action Args
2015-08-25 17:34:56alecsandru.patrascusetrecipients: + alecsandru.patrascu, skip.montanaro, brett.cannon, gregory.p.smith, scoder, skrah
2015-08-25 17:34:56alecsandru.patrascusetmessageid: <1440524096.57.0.482692079979.issue24915@psf.upfronthosting.co.za>
2015-08-25 17:34:56alecsandru.patrasculinkissue24915 messages
2015-08-25 17:34:56alecsandru.patrascucreate