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.

classification
Title: Mismatch between Python 3.3 build environment and distutils compiler support
Type: compile error Stage:
Components: Windows Versions: Python 3.3
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: BreamoreBoy, loewis, mayaa, steve.dower
Priority: normal Keywords:

Created on 2013-03-07 03:06 by mayaa, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg183629 - (view) Author: Hc.Z (mayaa) Date: 2013-03-07 03:06
My python environment is Python3.3 in Windows 7 32-bit. I was installing Pandas package from source code, through Microsoft Visual C++ 2008 Express is installed in my computer, the installation process still failed and report a "Unable to find vcvarsall.bat" error.
I checked the problem reading the distutils.msvc9compiler.py module. Class method find_vcvarsall() and query_vcvarall() works well, but get_build_version() return the 10.0. There is no mistakes about this, for sys.version print (MSC v. 1600) vs. in latest Python 2.7 it's (MSC v. 1500) which means vc2008. All document I found pointed that Python Windows binary was built through VC 2008 (version 9.0), and there is only msvc9compiler.py module, no msvc10compiler.py module. 
I don't know whether this is a bug, or there is another compatible mechanics I don't know.
After all, I just want to build Pandas correctly.
msg183633 - (view) Author: Hc.Z (mayaa) Date: 2013-03-07 06:05
My python environment is Python3.3 in Windows 7 32-bit. I was installing Pandas package from source code, through Microsoft Visual C++ 2008 Express is installed in my computer, the installation process still failed and report a "Unable to find vcvarsall.bat" error.
I checked the problem reading the distutils.msvc9compiler.py module. Class method find_vcvarsall() and query_vcvarall() works well, but get_build_version() return the 10.0. There is no mistakes about this, for sys.version print (MSC v. 1600) vs. in latest Python 2.7 it's (MSC v. 1500) which means vc2008. All document I found pointed that Python Windows binary was built through VC 2008 (version 9.0), and there is only msvc9compiler.py module, no msvc10compiler.py module. 
I don't know whether this is a bug, or there is another compatible mechanics I don't know.
After all, I just want to build Pandas correctly.



In addition, I've installed Visual C++ 2010 Express to install Pandas successfully.
msg224343 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-07-30 21:31
According to http://matthew-brett.github.io/pydagogue/python_msvc.html Python 3.3 has always been compiled with 2010 on Windows so I think this can be closed as "user sorted it out for him/herself" :)
msg224401 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-07-31 12:46
Installing VS 2010 express was indeed the right solution.
History
Date User Action Args
2022-04-11 14:57:42adminsetgithub: 61573
2014-07-31 12:46:37loewissetstatus: open -> closed
resolution: not a bug
messages: + msg224401
2014-07-31 00:28:41pitrousetnosy: + loewis, steve.dower
2014-07-30 21:31:21BreamoreBoysetnosy: + BreamoreBoy
messages: + msg224343
2013-03-07 06:05:30mayaasetmessages: + msg183633
2013-03-07 03:06:46mayaacreate