> they're saying that the Python 2/3 breakage debacle became a model for how packages are maintained in general. As explained above, semver is not a solution.

> they're saying that the Python 2/3 breakage debacle became a model for how packages are maintained in general. As explained above, semver is not a solution. And it is often not really followed. For example, boost is breaking backwards compatibility some times, and this is causing problems, last not least because boost Python bindings are used in so many projects.