If you use Bash, change ~/.zshrc to ~/.bashrc. zshrc file only manages zsh instances, so be sure to check what your shell is and edit the associated dotfiles. If you need to double-check what your default shell is, you can run echo $SHELL. Note that I used single quotes with echo so it does not evaluate and expand the commands. Now every time we run a command in zsh, it will use the pyenv version of Python. Append that same syntax to the ~/.zshrc file: $ echo 'PATH=$(pyenv root)/shims:$PATH' > ~ /.zshrc Since zsh is officially macOS's default shell, I'll focus on it. That export statement (PATH=) will only change for this shell instance, so make it a permanent change, you need to add it to your dotfiles. Users /my_username /.pyenv /shims /python
If you don't change the path, here is the result: You must ensure the shell will find the version of Python run by pyenv, not the one installed by default (which is often called the system version). PATH determines where the shell searches for files by the name of the command. In order to use the version of Python through pyenv, it's essential to understand the shell's PATH variable. I could clone and compile it myself from source, but I prefer to manage packages like this through the Homebrew package manager: $ brew install pyenv
#Brew install python 3.5 mac series
Thankfully, pyenv exists to work around this series of complexities. I would happily talk about why I still think it should.) Installing and setting up pyenv (A note on the above: I know this makes no sense to seasoned Python developer, but it made sense to me at the time. It might seem logical to think the Python package manager pip could install it*, but that wasn't the case:Īlternatively, I could have downloaded that version from the official Python website, but how would I run it in on my Mac alongside my existing version of Python? Specifying the version of Python I intend to use every time I run the interpreter (python3.7 or python3.5 for example) seems error-prone at best. Recently, I tried to run a project on macOS that depended on Python 3.5.9, a version that I did not have installed on my system. That makes it important for me to regularly get those updates. Python 3 is developing steadily, and releasing new updates regularly. In January 2020, Python 2 reached end of life, and only Python 3 will be supported by the language's core maintainers from then forward. Similarly again, different releases are identified by a three-digit number known as a semantic version.įor many years, Python 2 was the commonly used major version of the programming language.
They have bugs, fixes, and updates like any of your favorite APIs and any other software. It's a strange concept at first, but programming languages change like any other software. While there are well-documented strategies for package management, there is another step necessary to ensure you are running the version of Python you need when you need it. Managing a local Python development environment continues to be a challenge, even for experienced developers.
pip3 freeze > requirements.txtĪt this point you can do pip3 install -r requirements.txt to reinstall everything you uninstalled. Save the requirements to file if you want to quickly re-install everything you're about to remove. TIL about pip freeze: freeze Output installed packages in requirements format. I figured I'd give you the quickness on what I did so next time this shit happens to someone, they have a handy reference. Tl dr TIL pygame is broken using homebrew Python3, so I decided to wipe my shit and start from scratch.
0 kommentar(er)
