Don't take this as me trashing on Python or Pythonistas. If you want to talk
about this in person, I'm usually at PyCon. I'm also usually in the packaging
BOF. Perhaps we can bring some of this up there this year?
> help. Work with upstream developers to understand what they're doing, encourageAnd just as many (if not more) that don't. As a result, we have to
> them to care about API stability and to use conventions like semantic
> versioning and deprecation warnings to reduce the impact of changes. There are
> plenty of developers who do care about backwards compatibility.
design the system to defend against this breakage.
> We could also have topic-specific extra repos, so that a user can add, say, aPPAMAIN would be nice for special cases like this, aye!
> Python-science repo to get newer versions of some packages by accepting a bit
> of extra risk associated with that. Neurodebian offers something like that, but
> in general it's hard to set up. Ubuntu PPAs are much easier to get set up, but
> don't build for Debian relases.