Explore >> Select a destination
|
You are here 
|
www.mackorone.com | ||
| | | | |
ljvmiranda.micro.blog
|
|
| | | | | I'm now a uv convert. I haven't really updated my Python tooling and workflow for the past two years. In fact, I've been using the same workflow ever since I started working: python -m venv venv source /venv/bin/activate # While in venv pip install -r requirements.txt But there's a lot of limitations in this workflow. For example, I'm limited by the Python version installed in my machine or it's hard to just install ad-hoc dependencies for my one-off scripts. | |
| | | | |
dhariri.com
|
|
| | | | | The website of David Hariri, a software developer, designer, and entrepreneur. | |
| | | | |
www.silveiraneto.net
|
|
| | | | | ||
| | | | |
blog.nuculabs.de
|
|
| | | Hello, In this article I will introduce you to pyenv, a tool for managing python environments. Installing pyenv is pretty straight forward, you'll need to clone the repo and add the binaries to the path. For a typical Debian based distro using the Zsh shell the instructions would be: 1 2 3 4 git clone https://github.com/pyenv/pyenv.git ~/.pyenv echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zshrc Then, in order for this to take effect, you need to reload the shell with: source ~/.zshrc, or just restart your terminal. ?? | ||
