[issue7068] 2.6.3 does not use specified compiler

Tarek Ziadé added the comment: Done in r75269. Thanks Shun-ichi and Marc-André -- status: open -> closed ___ Python tracker ___ ___ Py

[issue7068] 2.6.3 does not use specified compiler

Barry A. Warsaw added the comment: Tarek, please commit this fix before 2.6.4rc1 (i.e. asap :) -- priority: -> release blocker resolution: -> accepted ___ Python tracker ___ __

[issue7068] 2.6.3 does not use specified compiler

Tarek Ziadé added the comment: Thanks for noticing, I'll rename it in the maintenance branch, but I need to wait for Barry to give me the green light since the 2.6 branch is frozen right now. -- nosy: +barry ___ Python tracker

[issue7068] 2.6.3 does not use specified compiler

Marc-Andre Lemburg added the comment: Thanks for reporting this. It appears that Benjamin tried to undo the .compiler attribute renaming Tarek had applied and r72586, but forgot to change back line 303 to the original version: {{{ # Setup the CCompiler object that we'll use to do all t

[issue7068] 2.6.3 does not use specified compiler

New submission from Shun-ichi Goto : I installed python 2.6.3 on windows from .msi installer and get problem to build ext modules with MinGW compiler. It seems that Python 2.6.3 does not use compiler specified by user via --compiler=xxx or setup.cfg on building ext module. Thus, MSVC compiler is