/explore
|
You are here 
|
www.mackorone.com | ||
| | | | |
www.silveiraneto.net
|
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
janakiev.com
Python's built-in venv module makes it easy to create virtual environments for your Python projects. Virtual environments are isolated spaces where your Python packages and their dependencies live. This means that each project can have its own dependencies, regardless of what other projects are doing. |
|
| | | | | ||
| | | | |
github.com
Simple Python version management. Contribute to pyenv/pyenv development by creating an account on GitHub. |
|
| | | |||
