Damus
Veit Schiele · 38w
nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyq8x5zejz4qweclr693fjxaw6ect6mjerjdyjcu0y86uun6r5v40vgyrp9z We found the workflow with requirements.txt too error-prone, especially when the vers...
Michael Kennedy profile picture
@nprofile1q... Makes sense. I never never edit requirements.txt. I have a "what am I actually using" file that looks like unpinned requirements.txt. Then use uv pip compile to generate requirements.txt. That works really well for me. Merge conflicts are very rare, can be tossed and regenerated at any time.
1
Veit Schiele · 38w
nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyq8x5zejz4qweclr693fjxaw6ect6mjerjdyjcu0y86uun6r5v40vgyrp9z Ah, I see. We have the unversioned dependencies in pyproject.toml. We then update our applications with uv lock --upgrade or uv lock --upgrade-package {PACKAGE}.