I am new in computer vision.
I am trying to install the opencv library 3.2 with python 3.6 but I followed every tutorial.
However; I don't know what I've done wrong. I have installed python 3.6 amd 64 and added it to the PATH ... then I have downloaded the wheel of opencv 3.2 for python 3.6 amd 64 then try to install it using pip.
However, it says that isn't supported in this platform. So, I don't know what to do now. I'm trying to avoid the CMake ... stuff because I find it tough!!!
The error mentioned in the prompt
Pip checks whether name of a wheel contains platform specific words Eg.
ad3‑2.0.2‑cp27‑cp27m‑win32.whl
(python 2.7, windows 32-bit/x86) if I install it on python 3.6 it say it isn't supported on this platform but if I change wheel's name it trys to install it. Chceck which pip are you really using. You can't use x64 wheels on x86 interpreter. Some unofficial wheels for windows platform you can find here: http://www.lfd.uci.edu/~gohlke/pythonlibs/
Related
I have been trying to install PySide6 on my PC (Windows 10 64bits) with Python 3.9.0 installed, but I keep getting errors every time.
I used the command pip install PySide6 It is not working for me.
Any help will be appreciated.
Error:
ERROR: Could not find a version that satisfies the requirement pyside2 (from versions: none) ERROR: No matching distribution found for pyside2
Check if you Python installation is 64 bit and not 32 bit. It has an impact on compatible and thus available binaries.
At the time of writing:
The problem is that most of the binaries are not yet compatible and are not yet compiled for Python 3.9 at the time of writing. If you want the best compatibility, use Python 3.7 or Python 3.8. Most of the packages have been compiled for Python 3.8 but not many for Python 3.9.
For the future people that come here:
I would recommend you to keep one minor version behind the current stable release to not face dependency problems as the above section explains.
For Example:
If current stable release is Python 3.12 then you should install Python 3.11 or Python 3.10. Just one or two versions behind the current stable release.
I'm trying to build Tensorflow from source (if I install directly it works fine but I'm trying to get AVX2/FMA extensions support as I can't use CUDA/GPU) and I'm following this tutorial to build Tensorflow 1.15 (which is needed for the project that I use, I can't use 2.x).
I've built Tensorflow successfully, but when I try to install the wheel with pip I get the following error:
ERROR: tensorflow-1.15.5-cp37-cp37m-macosx_11_0_x86_64.whl is not a supported wheel on this platform.
Well, I know what the error means but the problem is that:
The wheel, as implied by the filename, is built for:
Python 3.7
macOS 11.0
x86/64
Which is already what I have (yup, double checked Python version, it's exactly Python 3.7.9, and no I'm not on M1 if that matters, I'm on Intel Mac). Why am I getting this error message even though I'm on the platform that the wheel is built for?
UPDATE: I'm already on the latest pip as of writing, and I can verify pip and python point to the same version:
(tf) can#can-mbp tensorflow % which pip
/opt/anaconda3/envs/tf/bin/pip
(tf) can#can-mbp tensorflow % which python
/opt/anaconda3/envs/tf/bin/python
(tf) can#can-mbp tensorflow % pip -V
pip 21.0 from /opt/anaconda3/envs/tf/lib/python3.7/site-packages/pip (python 3.7)
(tf) can#can-mbp tensorflow % python -V
Python 3.7.9
FOR MACOS - BIG SUR
I was able to solve this problem when I found that the version of the macOS operating system does not match the version actually recognized by python
I'm using macOS 11.4, the file is with this version. But when typing a command in the terminal, I found that python recognizes 11.0.
python3
from distutils import util
util.get_platform()
>> 'macosx-11.0-arm64'
generated file name:
opencv_python-4.5.2+2344814-cp39-cp39-macosx_11_4_arm64.whl
new file name:
opencv_python-4.5.2+2344814-cp39-cp39-macosx_11_0_arm64.whl
Upon #Axe319's comment I took a look at https://github.com/apple/tensorflow_macos/issues/46 and seen that simply changing the wheel's filename's OS section to 10_9 works. There is probably a bug with parsing macOS 11.0 or Python doesn't think it supports 11.0 (maybe that particular Python/pip version was before Big Sur was released).
Make sure the Python version you are using (32/64 bit) does match what the wheel requires ;)
i cant able to install pip install robotframework-ride,getting error ,
ERROR: Command errored out with exit status 1:
installed robot frame work using pip and downloaded wxpython and installed at g drive in python folder for my convinence,kindly give solution friends
Because Python 3.9 is recent, some libraries, applications or modules are not compatible with it, or even tested. This is the case of RIDE that is having a Beta version compatible with Python 3.8, but not tested on Python 3.9.
The project page of RIDE is here.
About the error you found, it happened because your system is trying to build wxPython 4.0.7.post2 because there is no package for Python 3.9. Not even for version 4.1.1, exists a released package.
The project page of wxPython is here.
I have python 3.7.5 and Python 3.8 installed on the same windows 10 machine. They were both installed from python.org/downloads. When I run pip install coverage (using the latest release of pip) it installs coverage with c extensions under 3.7.5 and without c extensions under 3.8.2.
How can I force coverage to install with c extensions, as the performance is terrible without them?
It appears 3.7.5 downloads:
https://files.pythonhosted.org/packages/4b/c7/6b1af1c8806fa047469b19861a3438f9ce785aa41c831c15d676ccaaa726/coverage-5.0.3-cp37-cp37m-win32.whl
where as 3.8.2 downloads:
coverage-5.0.3.tar.gz
The later being "without c extensions"
There are no valid coverage wheel for Windows and Python 3.8 at the moment.
The 5.0.3 wheels on PyPI are marked as compatible with cp38-cp38m-win_amd64, so CPython 3.8, with the cp38m ABI variant, for 64-bit Windows.
But, there is no such ABI variant any more. Python 3.8 no longer has a m (--with-pymalloc) binary variant, because builds with or without --with-pymalloc are now ABI compatible.
Pip has followed suit and stopped adding the m flag when looking for wheels, and the wheel project, which creates these distribution files also dropped the m flag.
However, coverage.py is using an older release of wheel to build the distributions, they are using 0.33.1, while the above changes landed in version 0.33.5. You already filed a bug report with the project, I've added my findings there too.
Luckily, the flag is superficial. You can download the wheel file directly from PyPI, rename the file (removing the m from cp38m) and then use pip install path/to/renamed/coverage-5.0.3-cp38-cp38m-win_amd64.whl.
Note: the same issue applies to the 3.9 wheels.
I am new to python, and am trying to install some modules/packages using .whl file. The system does not have access to the internet so everything is local.
I'm running RHEL 6.9 64bit 2.6.32-696.10.1.el6.x86_64
Python is version 2.7.12 (altinstalled with 2.6)
platform.architecture()
('64bit', 'ELF')
I'm running pip 9.0.1
Attempt at installing numpy:
# /usr/local/bin/pip2.7 install numpy-1.13.3-cp27-cp27m-manylinux1_x86_64.whl
numpy-1.13.3-cp27-cp27m-manylinux1_x86_64.whl is not a supported wheel on this platform.
So what am I missing?
cp27-cp27m manylinux packages are compatible with a Python interpreter compiled with --enable-unicode=ucs2.
For an interpreter compiled with --enable-unicode=ucs4, you instead need cp27-cp27mu packages.