![anaconda cloud install pyqt5 anaconda cloud install pyqt5](https://i.ytimg.com/vi/LJNfV5H7EdA/hqdefault.jpg)
If using pip is dangerous in an Anaconda environment then either: A) there should be a bright red warning in the docs saying "NEVER USE PIP TO INSTALL A PACKAGE IF A CONDA PACKAGE IS AVAILABLE, IT MAY BREAK YOUR ENVIRONMENT" or B) a warning should be displayed when you actually use pip. As far as I'm concerned if you can irreparably break even a single environment by using pip, with no warning displayed, then that is a flaw in Anaconda. Incidentally, I still don't really understand why this issue was closed, because I don't see that any resolution was achieved. Are you saying that the fix only makes it so you can create a new environment with a working PyQt, but still irrevocably breaks any existing environments that had PyQt? Also, what happens if you pip-installed PyQt into the root environment? # but uninstalling and reinstalling pyqt qt in the broken qttest2 environment # doesn't seem to fix that : Thanks, that is good to know. $ python -c "from PyQt5 import QtCore print(QtCore._file_) " ~/anaconda/envs/qttest3/lib/python3.6/site-packages/PyQt5/QtCore.so $ conda create -n qttest3 python=3.6 pyqt # packages in environment at ~/anaconda/envs/qttest2: # $ conda create -n qttest2 python=3.6 pyqt $ python -c "from PyQt5 import QtCore print(QtCore._file_) " $ python -c "from PyQt5 import QtCore print(QtCore._file_) " ~/anaconda/envs/qttest1/lib/python3.6/site-packages/PyQt5/QtCore.so # packages in environment at ~/anaconda/envs/qttest1: # $ conda create -n qttest1 python=3.6 pyqt # create fresh environment for testing pyqt (The answer appears to be "install only the pip version and don't install the conda version before or after or you will break everything", but that's not stated anywhere that I can see.) In particular, it doesn't explain what to do if a package is available from both sources, but the conda version is older and you want the newer pip version.
![anaconda cloud install pyqt5 anaconda cloud install pyqt5](https://www.justintodata.com/wp-content/uploads/2020/03/anaconda-install.png)
Right now it just says "Others can be downloaded using the “pip install” command that is included and installed with Anaconda." This does not make clear that if a package is available from pip and from conda, you have to be careful because they will interact in funny ways.
![anaconda cloud install pyqt5 anaconda cloud install pyqt5](https://i.ytimg.com/vi/P3K4L7o58tg/mqdefault.jpg)
Since pip is unaware of conda but not the other way around, it would seem that the conda PyQt package should provide some kind of "purge" or "clear" option to detect existing pip-installed PyQt and erase it well and good, so that at least the conda PyQt can keep working.Īlso, I think the basic documentation (e.g., or ) should include some more overt warnings about this. However, being able to break your whole Anaconda installation by doing this seems a bit extreme. It is clear from #1554 that conda PyQt and pip PyQt5 shouldn't be combined in the same environment. (A similar issue was reported in #1554 but that discussion veered somewhat from the core issue of this breakage into a discussion about changing the conda package name.) The only way I could fix it was by uninstalling and reinstalling Anaconda entirely. Other environments also appeared to be broken. I tried every conceivable order of uninstalling and reinstalling the PyQt packages from pip and conda, but they didn't work. This broke the Qt installation such that apps like Spyder or even the Anaconda Navigator wouldn't load (either hard-crashing or giving a DLL load error). I wanted to upgrade, so I did pip install PyQt5. After installing Anaconda, I noticed the conda pyqt package only has Qt 5.6.