Re:Code that will break in Python 4
by jrochkind1 on Tuesday January 12, 2016 @12:59PM
(#10889040)
Well, baking it into dependency resolution is a response to the fact that figuring out if there were breaking changes in any given update becomes intractable as your dependency tree/graph gets large (and multi-levelled), when each dependency uses it's own versioning scheme, no matter how comprehensible they are individually.
[ Parent
| on HN ]
There are no comments on this comment yet.