I create python scripts daily and I use uv as a venv/dependency management.
Most of times, these scripts get zipped up and uploaded to a lambda or the script gets run in a pipeline job. They’re not for distribution.
I’m trying to configure pyproject.toml for this use case, I used to use requirements.txt but I found this to be outdated and often causes problems in my situation.
One thing I don’t understand about build modes, why do most venv managers require me to say which backend I want to use to build a distribution if I’m not planning on it?
Also which modes should I use? I see a lot of people mentioning editable, package, module, etc. I don’t understand it yet and docs I find online isn’t clear.
Additionally, is there any PEPs covering the scenario where it is one project but multiple independent packages? For example, I may have two lambdas, one does one thing and other does a different thing and is part of the same project but not part of the same package? Ideally I want this to be in one repo, but uv complains about that.
submitted by /u/BritishDeafMan
[link] [comments]
r/learnpython I create python scripts daily and I use uv as a venv/dependency management. Most of times, these scripts get zipped up and uploaded to a lambda or the script gets run in a pipeline job. They’re not for distribution. I’m trying to configure pyproject.toml for this use case, I used to use requirements.txt but I found this to be outdated and often causes problems in my situation. One thing I don’t understand about build modes, why do most venv managers require me to say which backend I want to use to build a distribution if I’m not planning on it? Also which modes should I use? I see a lot of people mentioning editable, package, module, etc. I don’t understand it yet and docs I find online isn’t clear. Additionally, is there any PEPs covering the scenario where it is one project but multiple independent packages? For example, I may have two lambdas, one does one thing and other does a different thing and is part of the same project but not part of the same package? Ideally I want this to be in one repo, but uv complains about that. submitted by /u/BritishDeafMan [link] [comments]
I create python scripts daily and I use uv as a venv/dependency management.
Most of times, these scripts get zipped up and uploaded to a lambda or the script gets run in a pipeline job. They’re not for distribution.
I’m trying to configure pyproject.toml for this use case, I used to use requirements.txt but I found this to be outdated and often causes problems in my situation.
One thing I don’t understand about build modes, why do most venv managers require me to say which backend I want to use to build a distribution if I’m not planning on it?
Also which modes should I use? I see a lot of people mentioning editable, package, module, etc. I don’t understand it yet and docs I find online isn’t clear.
Additionally, is there any PEPs covering the scenario where it is one project but multiple independent packages? For example, I may have two lambdas, one does one thing and other does a different thing and is part of the same project but not part of the same package? Ideally I want this to be in one repo, but uv complains about that.
submitted by /u/BritishDeafMan
[link] [comments]