[issue7511] msvc9compiler.py: ValueError: [u'path']

mike bayer added the comment: > I think it's fair to ask the user to setup the environment correctly before running "python setup.py install" We're supporting automatic fallback to non-C install for those environments that don't support it. We're just looking for a predictable CCompilerError

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: Marc-Andre Lemburg wrote: > Wouldn't it be better to have distutils tell the user about the > possible options, instead of guessing and then possibly compiling > extensions which later on don't import or import, but don't work > as expected ? That would be an opt

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Ryan Seto : -- nosy: -MrWerewolf ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue7511] msvc9compiler.py: ValueError: [u'path']

Marc-Andre Lemburg added the comment: mike bayer wrote: > > > > mike bayer added the comment: > > > > regarding "hey this is an MS bug not Python", projects which feature > > optional C extensions are starting to apply workarounds for the issue on > > their end (I will need to commit a spec

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: Hmm, in http://bugs.python.org/issue7511#msg106420 Tarek appeared to be supportive of the patch. Re DISTUTILS_USE_SDK: I don't think many users are aware of this variable. Also, it is not needed at all; it is sufficient to execute vcvars64.bat manually before ru

[issue7511] msvc9compiler.py: ValueError: [u'path']

Éric Araujo added the comment: Thorsten Behrens said: > You are right, this is not a bug in Python. The diff provides a > workaround for a limitation in VC++ 2008 Express. This diff is a > piece of user service. ipatrol added: > Purity shmurity. The point of distutils is largely to present a >

[issue7511] msvc9compiler.py: ValueError: [u'path']

mike bayer added the comment: regarding "hey this is an MS bug not Python", projects which feature optional C extensions are starting to apply workarounds for the issue on their end (I will need to commit a specific catch for this to SQLAlchemy) - users need to install our software and we nee

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Ralf Schmitt : -- nosy: +schmir ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: Going through more than a few registry keys, here are some that stood out for me: "HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\v6.0A" InstallationFolder "HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\v6.1" InstallationFolder "HKEY_CU

[issue7511] msvc9compiler.py: ValueError: [u'path']

Thorsten Behrens added the comment: Confirmed that this issue exists on Python 3.1 and 3.2b2. The exception thrown presents as: ValueError: ['path', 'include', 'lib'] -- ___ Python tracker ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: Purity shmurity. The point of distutils is largely to present a unified and simple interface. 'python setup.py install' should be all a user has to do on any platform. Unless you can come up with a better idea, MSVC is really the only big compiler on Windows. -

[issue7511] msvc9compiler.py: ValueError: [u'path']

Thorsten Behrens added the comment: You are right, this is not a bug in Python. The diff provides a workaround for a limitation in VC++ 2008 Express. This diff is a piece of user service. An equally as workable workaround is for the user to copy VC\bin\vcvars64.bat into VC\bin\amd64\vcvarsamd

[issue7511] msvc9compiler.py: ValueError: [u'path']

Martin v. Löwis added the comment: IIUC, the issue is that people installing a 64-bit Python, and VS Express, and then wonder why they can't build extension modules. I'm not so sure that there is a bug in Python here - this setup is not supported (and that's really Microsoft's fault). Now, au

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: Before anyone does any further testing: Tarek, can this go into distutils 2.7/3.2 (after 3.2 has been released)? Due to the popularity of this issue I think it might be worthwhile to make an exception and ignore the distutils freeze. -- _

[issue7511] msvc9compiler.py: ValueError: [u'path']

Thorsten Behrens added the comment: I can test this for 3.1, as all I have is the Express version of VC++. If you could point me towards a library that will work with 3.1 and has C components, that'll make the testing a lot easier. pycrypto and setuptools, the two libs mentioned in this issue

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue7511] msvc9compiler.py: ValueError: [u'path']

Ryan Seto added the comment: I came across this issue while trying to install mercurial using easy_install. I applied the vcvars4.diff to my distutils and this solved the problem. Environment: Python 2.6.6 (64 bit) setuptools-0.6c11.tar.gz installed using the following instructions: http://

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: > Stefan (sorry for the misattribution in my previous message), can you test > with 3.2 and 3.1 and adjust versions if needed? Not easily at the moment. I just noticed that I replaced my only Express installation with a Pro trial-edition. Anyone else? -

[issue7511] msvc9compiler.py: ValueError: [u'path']

Éric Araujo added the comment: Stefan (sorry for the misattribution in my previous message), can you test with 3.2 and 3.1 and adjust versions if needed? -- ___ Python tracker _

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Éric Araujo : -- Removed message: http://bugs.python.org/msg113641 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Christopher Paolini : -- nosy: -Christopher.Paolini ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7511] msvc9compiler.py: ValueError: [u'path']

Éric Araujo added the comment: Sridhar, can you test with 3.2 and 3.1 and adjust versions? -- nosy: +eric.araujo versions: -Python 2.6 ___ Python tracker ___ ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: HAHA DISREGARD THAT, WRONG DOWNLOAD. However, the C++ compiler `is` now installed by default. P.S: that second ValueError? -- ___ Python tracker ___ _

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: I noticed that the directions from mathworks are no longer correct. The only optional feature is a 64 bit SQL server. Yet I still can't get it to work correctly. Does MS no longer provide the compiler in their free editions? -- _

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: Aren't there two ValueErrors in the file? One is a platform and (in the now-fixed version) the other would indicate a problem with I/O or vcvars execution (like permissions). -- ___ Python tracker

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: ipatrol, thanks, I forgot to change ValueError. New patch attached. -- Added file: http://bugs.python.org/file17959/vcvars4.diff ___ Python tracker ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: Actually, I forgot the 64 bit directions X-? It will take some time for everything to download. But I did apply the patch and it did give me the "64 bit SDK not installed" error. Also, I think the tow ValueErrors should be changed to DistutilsPlatformError and Distu

[issue7511] msvc9compiler.py: ValueError: [u'path']

Martin v. Löwis added the comment: ipatrol: have you actually tested the patch? If so, which specific version, and on what specific Python version? -- ___ Python tracker ___ ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

ipatrol added the comment: May I request we resolve this by folding this patch into the main source tree for the next bugfix release? -- components: +Windows ___ Python tracker

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Stefan Krah : Removed file: http://bugs.python.org/file17952/vcvars3.diff ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Stefan Krah : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/optio

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: New version of the patch with a default value for arch. -- Added file: http://bugs.python.org/file17952/vcvars3.diff ___ Python tracker ___ ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: New version for the patch with a default value for arch. -- Added file: http://bugs.python.org/file17951/vcvars3.diff ___ Python tracker ___ __

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: I've been looking at this again because of new duplicate reports. I think we need to distinguish between amd64 and x86_amd64/x86_ia64. But using arch="x86" as the default parameter would do fine. Re unit test: The test will only work if 64-bit tools from the S

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Sridhar Ratnakumar : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue7511] msvc9compiler.py: ValueError: [u'path']

Mark Dickinson added the comment: Closed issue 9224 as a duplicate of this one; merging nosy lists. -- nosy: +ipatrol, mark.dickinson ___ Python tracker ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: I agree with all points. Could you fix it directly if at all possible? Of course eventually I'd do it, it might take some time until I get around to it though. -- ___ Python tracker _

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Terry J. Reedy : -- nosy: -tjreedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue7511] msvc9compiler.py: ValueError: [u'path']

Tarek Ziadé added the comment: Remarks with the patch: - we need to keep the find_vcvarsall() backward compatible. e.g. define a default value for arch. - Next, since this fix is specific to 64bt and since *any value* in arch will be used as "not 64 bits", I think the patch should be using a

[issue7511] msvc9compiler.py: ValueError: [u'path']

Tarek Ziadé added the comment: Yes I used 'accepted' to mark this issue as something I am working on. I am confused about the resolution flag, I think it is a bit overlapping with the status flag, and overcomplex. Maybe we should replace "closed" with various flags like: "fixed", "wontfix",

[issue7511] msvc9compiler.py: ValueError: [u'path']

R. David Murray added the comment: Some committers have been using 'resolution: accepted' as a way to mark issues that are definitely going to be fixed/enhancement added. For a critical bug I think this is a bit redundant (it is more useful for feature requests), but I'm pretty sure Tarek di

[issue7511] msvc9compiler.py: ValueError: [u'path']

Terry J. Reedy added the comment: Tarek, when you set the resolution to 'accepted', did you mean to close this? Resolutions are meant for closed issues. -- nosy: +tjreedy ___ Python tracker ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

Christopher Paolini added the comment: I'm running into the same issue myself. I even installed Visual Studio 2008. Issue is it installed as a 32-bit application in the x86 directory, not sure why. I have 64-bit Windows 7. I'm installing the SDK to see if that helps. Also I need this for pycr

[issue7511] msvc9compiler.py: ValueError: [u'path']

Changes by Tarek Ziadé : -- priority: -> critical resolution: -> accepted ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: 'ValueError' should be 'DistutilsPlatformError' in the diff. -- ___ Python tracker ___ ___ Python-bugs-

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: Ok, I created a new diff that considers all 64-bit values for 'arch'. I think x64 cannot occur (See: PLAT_TO_VCVARS). Also, I use the existence of bin\amd64\vcvarsamd64.bat as a test for VS Professional, so in that case the new code is never executed. Could someon

[issue7511] msvc9compiler.py: ValueError: [u'path']

Tarek Ziadé added the comment: OK so bin\vcvars64.bat would be an alternative location to look at for win32-64. Your diff says "amd64", shouldn't it be testing for "x86_64", "amd64" and "x64" ? -- ___ Python tracker

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: I needed a new Windows VM image anyway, so I can now confirm that the paths of a fresh VS Express + SDK 64-bit tools install are broken as described above. -- ___ Python tracker _

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: I think we have two issues here: First, the default install of VS Express does not support 64-bit tools, so distutils cannot work with a 64-bit Python install. I verified that it _does_ work with a 32-bit Python install. Second, it is possible to install 64-bit

[issue7511] msvc9compiler.py: ValueError: [u'path']

Tarek Ziadé added the comment: That's what distutils does : it runs vcvarsall.bat and pass as the argument the architecture. Can you run: $ vcvarsall.bat arch (replace arch by x86 or x64) and paste me the result ? (it looks like the 'path' variable misses from this file. -- __

[issue7511] msvc9compiler.py: ValueError: [u'path']

Stefan Krah added the comment: I have the same issue with the Express edition. You can work around it by finding and executing vcvars32.bat or vcvars64.bat before running setup.py. It would be nice if distutils took care of it though. -- nosy: +skrah ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

Sridhar Ratnakumar added the comment: I have Visual C++ 2008 express edition installed. Maybe it is a quirk of express edition as I was able to install pycrypto fine with the Visual Studio 2008 professional edition at work machine. In any case, I believe this is a bug with distutils. ---

[issue7511] msvc9compiler.py: ValueError: [u'path']

Martin v. Löwis added the comment: Most likely, the problem is that visual studio is not installed on your system. -- nosy: +loewis ___ Python tracker ___ ___

[issue7511] msvc9compiler.py: ValueError: [u'path']

New submission from Sridhar Ratnakumar : Win XP 64-bit Python 2.6.4 64-bit Getting distribution for 'pycrypto>=1.9'. Traceback (most recent call last): File "", line 1, in File "build\bdist.win-amd64\egg\setuptools\command\easy_install.py", line 1714, in main File "build\bdist.win-amd64