![]() Pyenv - is the the "de facto" framework to have multiple Python versions in the same system. The correct way to have various, and newer, Python versions in a Linux is to build them to other prefixes (even in the user home, no need for a global Python with other versions), and them leverage on virtaulenvs so that each project, or scratch directory for scripts one have, use the exact desired interpreter. For more than 10 years now, most Linux distributions rely on Python for critical system tasks, including package managing - and replacing the very files of the system Python packages will make all Python extensions in the system utilities to break at once. Add the following lines: echo 'eval "$(pyenv init -path)"' > ~/.zprofileĮcho 'eval "$(pyenv init -)"' > ~/.One should not try to replace the system Python install in any Linux distribution: it will just take your system into an unusable state. Open Terminal, then type in: brew install openssl readline sqlite3 xz zlibįinally, update the shell profile configuration, i.e ~/.zshrc if your default shell is ZSH. To make pyenv work, install build dependencies through Homebrew. The Homebrew Python documentation recommends pyenv to manage Python environments. ![]() You lose control over “site-packages” and all the PIP packages that you had installed might become inaccessible. For example, the "youtube-dl" package uses Python as its dependency, the Python package may get updated as and when needed. ![]() ![]() Many people prefer to use Homebrew to install software packages, but should you use it for Python development? The problem with using Homebrew Python is that it’s not in your control. If you’re working on multiple Python projects, the default location, which needs sudo privileges, creates hurdles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |