-
Notifications
You must be signed in to change notification settings - Fork 315
WPCP returns "package installed", but it failed #641
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
Comments
mayavi as "tons" of dependancies. you may run "pip install [path to mayavi wheel]" to captures the error messages describing all the wheels that may miss you. then download from cgohlke and install them first |
also, you could say the same for holoviews that depends of "anaconda" stack, but WinPython implements most of "anaconda" stack, while mayavi is mainly "enthought" stack that is not included per default, as it was mostly Python-2.7 until very recently. |
This is exactly what I did, installed using pip. That's when I saw the error messages. But I think WPCP should at least show a pop-up or something. Or do not remove the entry of the package in show the list with the packages to be installed and add "Failed" in red or something. Currently the user is not informed at all and has do dig through the list of all installed packages and check if the package is there now or if the version has changed. Does |
WPCP was making sense when it was created, before "pip" birth date. Now, it's just a basic layer over "pip", that I keep until "pip" project and friends provide a graphical interface. in french term, working on a graphical layer over pip myself would be "être plus royaliste que le roi". |
I was trying to install
mayavi‑4.6.0+vtk81‑cp36‑cp36m‑win_amd64.whl
for WinPython64-3.6.5.0Qt5 (Windows 7) using WPCP.Everything looked normal, the command window (wpcp started via .bat) said
OK
, as with other packages.But the list of packages did not show the package. When I used
pip install
with the wheel I saw that it failed because the compiler was missing.The text was updated successfully, but these errors were encountered: