this post was submitted on 28 Nov 2024
452 points (88.2% liked)

Programmer Humor

32692 readers
345 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] eager_eagle 4 points 2 weeks ago* (last edited 2 weeks ago)

yeah, all that setup sucks even after being writing python for years.

Nowadays I've been running every project with uv and it's a much better and faster experience, usually in 3 steps: 1. initialize, 2. add dependencies, 3. run project:


# if the project doesn't already have a pyproject.toml with dependencies, initialize it
# uv will also install the right interpreter if not present:
uv init --python 3.13

# anything you would install with pip, use uv add:
uv add dep1 dep2

# run the project / script
uv run main.py

Then in future runs (as long as you have the pyproject.toml), you can just do uv run main.py (shorthand to uv run python main.py), even when there's no venv created. No more activating virtual envs. No more long interpreter installations. No more accidentally messing with system's packages or the PATH variable. With the uv.lock that's also a lot more reliable to reproduce than requirements.txt and similar.