nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqyq8x5zejz4qweclr693fjxaw6ect6mjerjdyjcu0y86uun6r5v40vgyrp9z Ah, that explains it. We don’t use uv.lock for our libraries either, but we do use ...
@nprofile1q... Nice. Yes, I just find reading/using requirements.txt to be easiest on git diffs and are the most general for teaching too (you don't have to pick a toolchain and understand it to use it). So I generally stick to that. I have used it on one or two packages lately.
1