this post was submitted on 06 Nov 2024
202 points (98.1% liked)

Programming

17668 readers
169 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
202
Is Python's tooling incredibly difficult, or am I just stupid? (sh.itjust.works)
submitted 1 month ago by zaphodb2002@sh.itjust.works to c/programming@programming.dev
115 comments fedilink hide all child comments
 

So I'm no expert, but I have been a hobbyist C and Rust dev for a while now, and I've installed tons of programs from GitHub and whatnot that required manual compilation or other hoops to jump through, but I am constantly befuddled installing python apps. They seem to always need a very specific (often outdated) version of python, require a bunch of venv nonsense, googling gives tons of outdated info that no longer works, and generally seem incredibly not portable. As someone who doesn't work in python, it seems more obtuse than any other language's ecosystem. Why is it like this?

you are viewing a single comment's thread
view the rest of the comments
[–] iii@mander.xyz 30 points 1 month ago (3 children)

I still do the python3 -m venv venv && source venv/bin/activate

How can uv help me be a better person?

[–] GBU_28@lemm.ee 13 points 1 month ago (1 children)

And pip install -r requirements.txt

[–] BeardedGingerWonder@feddit.uk 13 points 1 month ago (3 children)

Fuck it, I just use sudo and live with the consequences.

[–] Swedneck@discuss.tchncs.de 3 points 1 month ago

the software equivalent of leaving the dirt on your vegetables to harden your immune system

[–] bamboo@lemm.ee 1 points 1 month ago

You’ll see when you start your second project why this doesn’t work.

[–] NostraDavid@programming.dev 7 points 1 month ago (1 children)
  1. let pyproject.toml track the dependencies and dev-dependencies you actually care about
  • dependencies are what you need to run your application
  • dev-dependencies are not necessary to run your app, but to develop it (formatting, linting, utilities, etc)
  1. it can track exactly what's needed ot run the application via the uv.lock file that contains each and every lib that's needed.
  2. uv will install the needed Python version for you, completely separate from what your system is running.
  3. uv sync and uv run <application> is pretty much all you need to get going
  4. it's blazingly fast in everything
[–] iii@mander.xyz 2 points 1 month ago

Thank you for explaining so clearly. Point 3 is indeed something I've ran into before!

[–] PartiallyApplied@lemmy.world 3 points 1 month ago

If you’re happy with your solution, that’s great!

uv combines a bunch of tools into one simple, incredibly fast interface, and keeps a lock file up to date with what’s installed in the project right now. Makes docker and collaboration easier. Its main benefit for me is that it minimizes context switching/cognitive load

Ultimately, I encourage you to use what makes sense to you tho :)