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?
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
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!
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.
Ohhh now I get it. It’s basically like
package.jsonandpackage-lock.jsonin node, but for Python.It’s a bit strange to me that this isn’t the default in Python…
Yes exactly, like if I know my app needs the requests library, I will just put that in
requirements.inbut after compilerequirements.txtwill 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