Programmer Humor

43205 readers

1 users here now

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

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 7 years ago

MODERATORS

cat_programmer@lemmy.ml

120

Thank you IntelliJ (lemmy.ml)

submitted 2 weeks ago by Mickkc@lmy.ndu.wtf to c/programmerhumor@lemmy.ml

24 comments fedilink hide all child comments

I was just editing my Dockerfile and suddenly IntelliJ showed me the message "No" without any context.

you are viewing a single comment's thread
view the rest of the comments

[–] Mickkc@lmy.ndu.wtf 2 points 2 weeks ago (2 children)

I don't quite understand that. I did some research, and I read that the requirements.txt is somehow generated from requirements.in. But what is the difference between the two files then? Could you give me an example of what a requirements.in file would look like?

Thank you!

[–] scrion@lemmy.world 5 points 2 weeks ago

Please use a pyproject.toml file for both project setup and dependency management. It actually is standardized now in PEPs.

uv is a great tool, now comes with a build tool as well. It has become a de-facto standard.

[–] Mickkc@lmy.ndu.wtf 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Ohhh now I get it. It's basically like package.json and package-lock.json in node, but for Python.

It's a bit strange to me that this isn't the default in Python...

[–] bamboo@lemmy.blahaj.zone 3 points 2 weeks ago

Yes exactly, like if I know my app needs the requests library, I will just put that in requirements.in but after compile requirements.txt will include the exact version of requests and every version of each dependency. So that every time pip install is run, all dependencies are always the same despite what happens upstream