/explore
|
You are here 
|
janakiev.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. | |
| | | | |
www.joeltok.com
|
|
| | | | | Python dependency management for reproducibility, using built-in libraries. | |
| | | | |
koaning.io
|
|
| | | | | This feels like a fun thing to add to your `.zshrc` file. ```bash cd() { builtin cd | |
| | | | |
snarky.ca
|
|
| | | There are a couple of things I always want to be true when I install Python packages for a project: 1. I have a virtual environment 2. Pip is up-to-date For virtual environments, you would like them to be created as fast as possible and (usually) with the newest version | ||
