[issue14708] distutils's checking for MSVC compiler

Martin v. Löwis added the comment: In any case, it appears that there is no bug report in this issue, so I'm closing this as "works for me". -- resolution: -> works for me status: open -> closed ___ Python tracker

[issue14708] distutils's checking for MSVC compiler

Martin v. Löwis added the comment: DISTUTILS_USE_SDK really means "shut up, I know what I'm doing". So if this is the case (i.e. you *really* know what you are doing), just set MsSdk as well. I don't actually know whether the latest SDK is able to build correct extensions for Python 2.7 - I h

[issue14708] distutils's checking for MSVC compiler

jamesf <54740...@qq.com> added the comment: Thanks for your replying. Here is my understanding of how the compiler chosen logic works, correct me if i am wrong: 1) If using MSVC, we should ALWAYS stick the compiler to the version which python was compiled with; 2) But we can change SDK version

[issue14708] distutils's checking for MSVC compiler

Martin v. Löwis added the comment: > 1) The MSSdk environment variable is not set by lastest SDK's > SetEnv.cmd anymore, but distutils still check for it. This is intentional. Older SDKs still set the variable, so there is nothing wrong with checking it. > 2) I have also install MSVC 2010 Exp

[issue14708] distutils's checking for MSVC compiler

Changes by Antoine Pitrou : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue14708] distutils's checking for MSVC compiler

New submission from jamesf <54740...@qq.com>: I am using python 2.7.2 installed via the pre-built installer package, and my SDK version is v7.1. 1) The MSSdk environment variable is not set by lastest SDK's SetEnv.cmd anymore, but distutils still check for it. 2) I have also install MSVC 2010