this post was submitted on 10 Dec 2024
31 points (97.0% liked)

Python

6467 readers
18 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
31
Lazy self-installing Python scripts with uv (treyhunner.com)
submitted 1 week ago by [email protected] to c/[email protected]
7 comments fedilink hide all child comments
 

via https://mastodon.social/@treyhunner/113624679999224789

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 week ago (1 children)

Nope, pipx definitely can't do that, but the idea that running your yourscript.py --help will automatically trigger the downloading of dependencies and installing them somewhere isn't really appealing. I'm sure I'm not the only person who's got uv configured to install the virtualenv in the local .venv folder rather than buried into my home dir, so this would come with the added surprise that every time I invoke the script, I'd get a new set of dependencies installed wherever I happen to be.

I mean, it's neat that you can do this, but as a user I wouldn't appreciate the surprise behaviour. pipx isn't perfect, but at least it lets you manage things like updates.

[–] eager_eagle 1 points 1 week ago* (last edited 1 week ago)

I’m sure I’m not the only person who’s got uv configured to install the virtualenv in the local .venv folder

That's the default for projects. Script is a different run mode.

every time I invoke the script, I’d get a new set of dependencies installed wherever I happen to be.

Does that happen though? uv uses the cache location for these script dependencies, not your usual venv one. Where you call it from is not a factor.