4 ms·

> My understanding of semantic versioning is... ...irrelevant, I'm afraid. Python doesn't use semantic versioning, so you can't really expect them to follow i

by scbrg 6y ago

> My understanding of semantic versioning is... ...irrelevant, I'm afraid. Python doesn't use semantic versioning, so you can't really expect them to follow it. As GP insinuated, if you just pretend that 3.7 is 37, and 3.8 is 38, you'll pretty much be able to apply semver thinking, though.

dheera 6y ago
> Python doesn't use semantic versioning Right, so because Python doesn't coooperate, we end up needing containerization, which is what I was trying to explain in GGGGP. Because apt will upgrade 3.7 to 3.8 and unfortunately break anything that was written in 3.7 (and vice versa). An app needs to be able to say "I'm ok with python3>=3.7" and be fine if it gets 3.8, 3.9, or 3.20, if we want to be able to run it without a container. (And likewise for all its other dependencies besides python)