Because of the size of the installed pip packages , I moved the ~/.local/lib/python3.6 directory to another partition and then made a symlink(a.k.a shortcut for windows users) to it , and that had been worked fine.
But recently I installed a newer linux distribution which has python3.8 pre-installed and I want to re-use those python3.6 packages(since the minor version is the same) to obviate the need of re-installing them.(almost 3.5 GB)
I made a symlink (~/.local/lib/python3.8/ which is the exact name that pip creates itself) to /path/to/external/lib/python3.6 , but now python shell is unable to recognize those packages.
Any ideas?
Do I need to re-install them?
Thanks.
These projects have to be reinstalled. There is no compatibility guarantee between minor versions (or major obviously), only between maintenance versions.
Related
In changing the symlink to V3.11.1, I've "lost" access to all Python packages installed under 3.8.8. Aanconda can't find any modules either, either under 3.8 or 3.11 and won't let me reinstall Anaaconda.
At the terminal prompt, I can get to V3.11.1 via Python3 command (not Python) and can see a list of modules but none of the packages previously installed. Tried to reinstall Anaconda but the installer says to upgrade instead. When I try to upgrade at the system prompt, "conda" isn't recognized.
I'm know my references are all messed up but not sure how to get my environment working. Appreciate any help/suggestions.
I have had PyTorch 1.4 installed on my machine for a little while now, and just tried to install 1.5 using the directions found directly on PyTorch.org.
Unfortunately, it failed, as do most things I try to do exactly as told. No shocker there.
Now, I have some half-installation of PyTorch 1.5 that will not import, but insists that it's on my machine. It fails with a FileNotFoundError, referring specifically to caffe2_nvrtc.dll.
I found an issue on GitHub with this problem that was closed last month, but of course it still is an issue, and many other people have reported it since it was closed. There has been no real resolution.
I just want to go back. What is the best way of getting rid of 1.5 without screwing up my machine and its environments even worse? And then, where do I find v1.4? It is not listed on the "Previous PyTorch Versions" page.
The old versions are still available as before and you can install them directly with pip by specifying the version you want to install:
pip install torch==1.4.0 -f https://download.pytorch.org/whl/torch_stable.html
As you seem to be on Windows the -f https://download.pytorch.org/whl/torch_stable.html part is required, because the Windows versions are not distributed over PyPI, but you have get them from PyTorch's registry. There you can also find all the versions (including past versions) of PyTorch.
Installing an older version of the same package should remove the current one, but in case you run into problems with that, you can first uninstall PyTorch before you install the older version:
pip uninstall torch
2 pip are installed one is v 9 and other is v 19
how to update the pip to the latest version 19?
I m unable to download some packages due to this version conflict.
and I want only one latest pip version should be instaled, and it will be used in all the packages.
You have two different versions of python and pip installed. This is common.
/usr/local/lib/python2.7/dist-packages/pip was most likely installed by the operating system, and allows you to sudo pip install Python 2.7 packages.
/home/manish/.local/lib/python3.5/site-packages/pip is in your home folder, which means you shouldn't have to elevate your user privileges to pip install a package. This is for Python 3.5.
Managing Python versions and dependencies can be massively confusing, especially if you're just trying to follow along with a tutorial.
The best tool I can recommend to make sense of this is pyenv. It lets you install any version of python in your home folder, and allows you to switch between on a per-project (folder) basis by creating a .python-version file. pyenv.
To do this I ran just ran the command
pip3 install azure
and from what I could tell this retrieved the latest versions of the various Azure modules for Python3. For example, the Postgres version was listed as 2017-12-01 and networking was 2018-08-01. However, I ran the same command from two other Ubuntu systems and on these systems the Postgres version was much older, 2017-04-30-preview.
How do I insure that the latest stable versions of the Azure SDK modules are installed when I run the pip install command on a system?
After a lot more trouble than it should have been, I managed to get pip3 updated on these systems and then running
pip3 install azure
installed the latest versions of the Azure modules. I didn't realize the version of pip impacts which versions of external modules it installs but apparently it plays a role.
Sometimes pip install launches a lengthy compilation process. Sometimes it does not. This was most notable with numpy, because it takes significant time to compile but is negligible time when installing binaries. I have an Ubuntu 14 machine where it always compiles numpy, and an Ubuntu 16 machine where it never compiles.
I assumed that Ubuntu 14 packages were no longer available or something. But then I launched a brand new VM with this same older OS, and pip install numpy, went super fast (no compiling). So clearly it is not simply the OS version impacting me. What is going on here?
It's probably a difference in the version of pip you're using. Both binary and source wheels exist in pypi so the question is which will pip choose. I found that on the same machine, pip 1.5.4 would choose the source wheel but pip 9.0.1 would choose the binary one.
Newer versions of pip (ex. 9.0.1) have options for controlling this behaviour: https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-no-binary
I'm guessing maybe older versions of pip don't even support binary wheels.
So try upgrading pip and then it should install without compiling.