There's nothing we can/will do for 2.x at this stage. Hopefully, 3.5 will switch to the next version of MSVC (14) and will be able to detect and use all later releases, so this particular problem won't exist in the future. You can set DISTUTILS_USE_SDK=1 and run from the VS 2012 Developer Command Prompt (or otherwise configure your environment) if you are willing to accept the risk, but ensure you test the built extension thoroughly. Msvc9compiler should not look for any versions of MSVC other than 9.0, since extensions built using other versions will be subtly (or dramatically) incompatible with Python unless you also rebuild Python itself with the same MSVC version. This is a feature request and new features are only being added on the 3.x line. Has there been some sort of policy change within Python to stop supporting 2.x? I'd love for them to upgrade but it's not really in my control. I ask because all the application I depend upon only run against Python 2.x (Rhodecode, Mercurial, etc). Currently it complains "cannot find vcvarsall.bat".
#VCVARSALL.BAT PYTHON 3.5 DOWNLOAD INSTALL#
Ich habe ein 64-Bit-Win-7-Setup auf meinem PC. I tried all the methods that I can find online and I even dove into the python code it didn't help. Messages (12) msg296218 - Author: Steve Dower (steve.dower) Date: 22:03 Due to how installation of Visual Studio 2017 has changed, it's very possible to end up with a valid install of the build tools without vcvarsall.bat being valid.
Msvc9compiler needs to check for the VS110COMNTOOLS environment variable in order to support Visual Studio 2012. Microsoft Visual C ++ 14.0 ist erforderlich (vcvarsall.bat kann nicht gefunden werden) Ich habe Python 3.5 installiert und während der Ausführung.
BreamoreBoy, brian.curtin, cowwoc, steve.dower, tim.golden, trent, zach.wareĬreated on 23:52 by cowwoc, last changed 20:52 by steve.dower.
0 kommentar(er)
