/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.silveiraneto.net
|
|
| | | | | ||
| | | | |
www.rasulkireev.com
How to set up a virtual environment for your Django Project, or any other Python project, for that matter. |
|
| | | | | ||
| | | | |
iscinumpy.dev
Poetry provides a all in one solution to Python packaging. I want to focus on why I was quite hard on Poetry in my last post, specifically on its default version capping and solver quirks, and also a few other negative things. This is a followup to Should you have upper version bounds, which you should read before this post. |
|
| | | |||
