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.

Author giampaolo.rodola
Recipients amaury.forgeotdarc, eric.araujo, giampaolo.rodola, jafo, loewis, tarek
Date 2010-11-06.12:12:50
SpamBayes Score 0.00062212517
Marked as misclassified No
Message-id <1289045572.68.0.614559072568.issue4931@psf.upfronthosting.co.za>
In-reply-to
Content
I don't have the same setup I had at the time when I submitted the first message so maybe something has changed in meantime.
Below is what I get on Windows 2000 SP-3, no VS installed, python 2.7, before and after the patch.

C:\Documents and Settings\foo\Desktop\psutil>setup.py build
running build
running build_py
copying psutil\compat.py -> build\lib.win32-2.7\psutil
copying psutil\error.py -> build\lib.win32-2.7\psutil
copying psutil\_psbsd.py -> build\lib.win32-2.7\psutil
copying psutil\_pslinux.py -> build\lib.win32-2.7\psutil
copying psutil\_psmswindows.py -> build\lib.win32-2.7\psutil
copying psutil\_psosx.py -> build\lib.win32-2.7\psutil
copying psutil\_psposix.py -> build\lib.win32-2.7\psutil
copying psutil\__init__.py -> build\lib.win32-2.7\psutil
running build_ext
building '_psutil_mswindows' extension
error: Unable to find vcvarsall.bat


Although the message is improved ("Unable to find vcvarsall.bat" vs "None") it seems the patch had no effect.
History
Date User Action Args
2010-11-06 12:12:53giampaolo.rodolasetrecipients: + giampaolo.rodola, loewis, jafo, amaury.forgeotdarc, tarek, eric.araujo
2010-11-06 12:12:52giampaolo.rodolasetmessageid: <1289045572.68.0.614559072568.issue4931@psf.upfronthosting.co.za>
2010-11-06 12:12:51giampaolo.rodolalinkissue4931 messages
2010-11-06 12:12:50giampaolo.rodolacreate