-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows (old versions): DLL load failed error #810
Comments
Do you have any idea what's the issue?
|
@giampaolo Looks like you built only half of the wheels for 4.1.0 compared to 4.0.0. It only gives you the vcvarsall.bat error when an appropriate wheel could not be found and it tries to download/build from source.
vs
See https://www.python.org/dev/peps/pep-0427/#file-name-convention The I've run into this issue in the past, it has to do with pip/wheel wanting to use @Mark-Booth Can you upgrade pip and/or wheel? python -m pip install -U pip
pip install --upgrade wheel |
I ran into the same problem with python3 and pip 7.1.2.
Upgrade works:
|
I remember I upgraded pip/wheel to their latest versions because we bumped into this issue already so it seems that somehow simply upgrading pip/wheel is not enough. Also I am not sure I understand the nature of the problem. Even worse, my Windows VM is gone so I have to reinstall Windows and the various Visual Studio suites (I feel sick just to think about that lol), and since I will fly to US next Monday I am afraid the issue will remain open for a while unless someone is able to produce the necessary exes/wheels, in which case he/she can send it to me and I will upload them on PYPI. |
Related note: Appveyor (https://ci.appveyor.com/project/giampaolo/psutil) would technically be able to produce exes/wheels, which would be good because it would mean avoiding to install different VS versions, which is a real pain, but I am not sure if and where they get stored. Let's say this is just a personal note to remember to investigate Appveyor in this regard. |
Going back off of distant memory when I ran into this issue, the version of pip/wheel on the build machine is what caused it to build wheels with different There's an issue in the packaged version of pip/wheel of the Windows Python distribution that only looks for an Also when you create virtualenvs, it would use an old bundled version of pip even if there was a newer one available. |
Ok thanks for the precious input (I don't use virtualenvs BTW).
|
I configured AppVeyor which now is able to produce and upload wheels/exes.
I googled for |
@giampaolo these are coming from wheel (not from pip), but they're only warnings, and should not affect the actual wheel building. I'll need to apply the changes from pypa/pip#3383 to wheel (although I thought I already had) to suppress the warnings. |
Do the new 4.2.0 wheels (uploaded yesterday) have the same problem? I generated them on AppVeyor (not sure if that made any difference). |
I can't test your Windows wheels but they do all contain the cp* SOABI tags. That said, it looks like the build of Python 2.7 you're using is UCS-2, perhaps that is common on Windows, but most of the Linux world's builds are UCS-4. |
I tried installing via Windows and it attempted a source install. A quick fix would just be to rename the wheels to have |
Did pip show anything useful in the output before deciding to ignore the wheels and try the source? |
|
OK so I took a closer look at this by installing a fresh Win 10 box with no VS installed. I can reproduce the issue if I use pip 7.1.2 (as @mrjefftang) but after I upgraded pip ( |
On a second thought, if possible, perhaps it makes more sense to use the default pip version shipped with Python 2.7 and generate the wheels with that version of pip. |
Also here: https://bitbucket.org/pypa/wheel/issues/169/incompatible-wheels-on-windows-depending |
OK, I should have fixed this problem by creating the wheel with pip 7.1.2 and then by renaming the wheel adding a |
* origin/master: (121 commits) update HISTORY/README giampaolo#810: rename windows wheels to make pip 7.1.2 happy add doc warning about disk_io_counter() numbers which may overlap (se giampaolo#802) update HISTORY git travis/osx error fix typo fix travis err add STAT for ps.py Convert string arguments to bytes appveyor download script: check the num of download files and print a warning if it's < than expected win / CI: try not to upgrade pip version and see whether pip produces compatible wheels refactor makefile makefile refactoring makefile refactoring Updated to use better if/else/endif values (my bad) Updated HISTORY to explain better that Win XP still uses 32bit values Reverted test code, will add in a different PR Styling fixes (spaces instead of tabs) PEP 8 compliance and history update (Vista+ only for fix) Type fix Continue on RuntimeError when running df on partitions it can't run on Fix disk_usage test to use 1 kB block size due to issues with OS X Add comment lines to ifs for win versions Actually does need it in XP/2000 unfortunately Tried to keep the mingw32 support but win 7 sdk is causing issues Whoops, whitespace issue Add back in ws2tcpip.h in the proper place in Win XP / Win 2000 Fixes for compiling on Win XP/Win 200 Update HISTORY.rst with giampaolo#816 issue bug fix Fix for windows net_io_counters wrapping after 4.3GB due to MIB_IFROW using DWORD. Updated to use MIB_IF_ROW2 which gives ULONG values instead. This causes more breaking changes for Windows XP and all Windows versions less than Vista / Server 2008 meaning that it should have no problems working on Vista / Server 2008 and beyond. fix doc indentation doc indentation fix giampaolo#829: disk_usage().percent takes reserved root space into account giampaolo#829: add tests to compare disk_usage() with 'df' cmdline utility small refactoring update comment update badges move stuff around reorganize (move stuff in) _common.py def __all__ for _common.py module reorganize (move) test utils update __all__ small @memoize refactoring Fix psutil.virtual_memory() type mismatch for NetBSD. prettyfy code prettyfy code update README Sets Makefile variable for imports compatible with Python 3.x fix linux test memory_maps: use bytes fir unpackment err refactor smaps code linux memory_maps refactoring fix typo update doc update version and HISTORY re-enable win services re-enable all tests on windows try to upgrade pip try to upgrade pip try to upgrade pip try to install pip globally try to upgrade pip force build of old 4.1.0 ver giampaolo#817: add script to download exes/whels from appveyor appveyor exp 5 appveyor exp 4 appveyor exp 3 appveyor exp 2 appveyor/ci#806 (comment) appveyor exp appveyor/ci#806 (comment) appveyor experiment appveyor experiment appveyor: attempt differe VS config for py 3.5 fix typo restore previous appveyor conf + try to add python 3.5 64 bits try easier appveyor conf, see pypa/packaging.python.org#172 try to make appveyor create exes/wheels add freebsd dev notes refactor ctx switches uids/gids refactoring refactor num_threads more refactoring [Linux] Process.name() is 25% faster (on python 3) ignore me remove outdated test [Linux] speedup Process.status() by 28% [Linux] speedup Process.pid() by 20% by reading it from /proc/pid/stat instead of /proc/pid/status set ppid linux set ppid fix 813: have as_dict() ignore extraneous attribute names which getsattached to the Process instance pep8 fixes fix giampaolo#812: [NetBSD] fix compilation on NetBSD-5.x. build fix: MNT_RELATIME and MNT_EXTATTR are not available on NetBSD-5 build fix: declare warn() update IDEAS fix win tests better AD error handling on win service descr: handle unicode errors service descr: handle empty description str check PyUnicodeDecode return value add services memory leak tests update doc ...
Re-opening as Windows 2003 has the same issue (see #348). |
Closing as a duplicate of #936. |
Similar to issue #706 the current version of psutil doesn't appear to have windows installers.
If I do
pip install --user psutil
it gives me aerror: Unable to find vcvarsall.bat
, but it works fine if I dopip install --user psutil==4.0.0
.The text was updated successfully, but these errors were encountered: