-
Notifications
You must be signed in to change notification settings - Fork 317
Failures installing sounddevice wheel #423
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
oups ! This was unexpected a wheel name. I clearly didn't understood how to split wheels name in proper pieces. patch welcomed. In the mean time, You can use "pip install sounddevice" to install it via the command line. |
The computer where I am doing the installation is disconnected from the internet, but I have transferred the wheel file to it using the USB flash drive. Should I use an elevated "WinPython Interpreter.exe" to do the installation? I am confused about the pip command because the documentation I saw only downloads from the internet. WinPython already has all the dependencies of the sounddevice package. How do I install a wheel file that I already copied to my PC (with no internet connection)? |
if your wheel is on "e:\BigWheelTheory\sounddevice-0.3.5-py2.py3.cp26.cp27.cp32.cp33.cp34.cp35.cp36.pp27.pp32.pp33.pp34.pp35.pp36-none-win_amd64.whl" do pip install "e:\BigWheelTheory\sounddevice-0.3.5-py2.py3.cp26.cp27.cp32.cp33.cp34.cp35.cp36.pp27.pp32.pp33.pp34.pp35.pp36-none-win_amd64.whl" |
With WinPython-64bit-3.5.2.3Qt5, I tried using "WinPython Interpreter.exe" from the WinPython root with elevated privileges. This didn't work because the pip command is not found. Is it a bug that "WinPython Interpreter.exe" doesn't set up the path? I succeeded by using "WinPython Command Prompt.exe" from the WinPython root with elevated privileges, and typing the following command:
pip checked the dependencies during the installation. I don't know if the -m option was important, but it is suggested at https://pypi.python.org/pypi/sounddevice/ I can now import sounddevice from the console in Spyder. Also, sounddevice 0.3.5 now appears in the WinPython Control Panel. I hope this means I can uninstall sounddevice from the WinPython Control Panel if I need to. |
"python -m pip" is needed to upgrade pip, as "pip.exe" directly would lock the "pip.exe" object and made the upgrade impossible. for all other packages "pip install" is just nice |
Thanks for the explanation. I have started testing sounddevice, so I can now declare that sounddevice is compatible with 64-bit Python 3.5. Therefore, this PR is with WinPython Control Panel and/or wppm. @stonebig - Please identify the WinPython project source file that splits a wheel name into proper pieces. This will improve the chances that a kind soul will offer a patch. |
How about adding a "Help Wanted" label? |
@stonebig - Your instructions for using pip to install a local wheel (or pure Python source) file were very helpful to me, including the explanation about the -m option. I suggest updating the following page to help others who also encounter problems with wppm or WinPython Control Panel: |
please do |
any news on this decoding ? I don't find a simple using internal pip wires. I may have to do it myself |
I may use .split(), much simpler to understand |
ok, next version will allow to install imageio via wppm |
Since I could not get PyAudio to work with the WDMKS api that I desire, I attempted to install the wheel "sounddevice-0.3.5-py2.py3.cp26.cp27.cp32.cp33.cp34.cp35.cp36.pp27.pp32.pp33.pp34.pp35.pp36-none-win_amd64.whl" from https://pypi.python.org/pypi/sounddevice/ into 64-bit WinPython 3.5.2.2.
I tried elevated WinPython Control Panel and "wppm -i" from the elevated WinPython Command Prompt, and both threw an error saying the file is not recognized. I thought it might be the file name length, so a made copy to a short file name. With both methods, the file was then recognized, but I still got an error saying the wheel is not compatible with 64-bit Python 3.5.
This PR is 2 problems:
The text was updated successfully, but these errors were encountered: