Short answer: You can’t, as far as I know. It wouldn’t really work either, right? If you use pyenv virtualenv to install a virtualenv into a repo, and you clone that repo to another machine… how would pyenv on the new machine know to take control of the virtualenv in the repository? Also, “you probably shouldn’t … Read more
I faced this issue because when I executed brew install, brew updated the patch version of Python from 3.9.13_1 to 3.9.14. This can be easily resolved by running the following to uninstall and then install poetry. curl -sSL https://install.python-poetry.org | python3 – –uninstall curl -sSL https://install.python-poetry.org | python3 –
When is an unique directory for virtual environments used? Which option is recommended? Why? Every virtual environment “lives” in its own folder. All packages you install will go there, especially if every environment will have a different Python version. How should I install per-project packages listed above? When you switch to the project environment after … Read more
pyenv seems to require explicit .python-version file to be set in the current directory for any other version than the default in .pyenv/version. This is explained in a closed GitHub issue. The problem is fixed by creating .python-version file. This is done automatically for example by $ pyenv local 2.7.10. The initial problem therefore is … Read more
Here is how you can switch to 3.9.0 for a given virtual environement venv-name: pip freeze > requirements-lock.txt pyenv virtualenv-delete venv-name pyenv install -s 3.9.0 pyenv virtualenv 3.9.0 venv-name pyenv activate venv-name pip install -r requirements-lock.txt Once everything works correctly you can safely remove the temporary requirements lock file: rm requirements-lock.txt Note that using pip … Read more
I ran into the same issue on macOS today. Turned out that you need to run the installed app once, it does some additional downloading and setup. That setup includes setting up your path variables.
I’m not sure if that solution matches the problem, but after installing pyenv, pyenv-virtualenv and selecting a python version, I had to run pip that way: $ pyenv exec pip install
These are the relevant parts of your log: In file included from /tmp/python-build.20210602162502.2268/Python-3.9.4/Modules/_cursesmodule.c:113: ./Include/py_curses.h:36:10: fatal error: curses.h: No such file or directory 36 | #include <curses.h> | ^~~~~~~~~~ compilation terminated. /tmp/python-build.20210602162502.2268/Python-3.9.4/Modules/_ctypes/_ctypes.c:107:10: fatal error: ffi.h: No such file or directory 107 | #include <ffi.h> | ^~~~~~~ compilation terminated. Python build finished successfully! The necessary bits to … Read more
Alright, I figured the problem. A little embarrassingly, I had not run pyenv shell 3.8.1 before running any of the other commands. Everything works now. Thank you all for your efforts.
When using pyenv, you should be able to set your ‘local’ version in the directory you are working in, and then pip will rely on this version. So in your case: pyenv local 2.7.14 pip install package-name See more on pyenv commands here: https://github.com/pyenv/pyenv/blob/master/COMMANDS.md But I do think the main piece that is missing here … Read more