Structured, Exchangeable lock file format (requirements.txt 2.0?)

For those interested, I wrote down what I current have in mind for the lock file, including things I learned both from Pipenv.lock, poetry.lock, and various thoughts from this thread:

I’m quite sure this is not perfect, I may have missed something (even from this thread), and there are still holes in the proposal that needs to be plugged, but I’m quite happy with the general strcuture of things I’ve come up with. Hopefully this can be the basis of a PEP if you (everyone in this thread and more!) could correct me and extend on the idea :pray: