News for hackers. Stuff that matters.

A comment on Removing Python 2.x support from Django for version 2.0. Parent comment

Re:Removing Python 2.x support from Django for version 2.0 by etatoby on Thursday January 19, 2017 @06:02AM (#13434801)
> warn users with a deprecation warning in one version and then they make the backwards incompatible change in the next version

That's exactly how _not_ to break backwards compatibility.

[ Parent | on HN ]
Re:Removing Python 2.x support from Django for version 2.0 by zmb_ on Thursday January 19, 2017 @07:45AM (#13435292)
That is, by definition, breaking backwards compatibility. I.e., the code that I wrote against version X will not run against version X + n. They just give a warning about it in version X + (n - 1). Backwards compatibility means that my code will run against X + n for all values of n >= 0 without modifications.
[ Parent | on HN ]
Re:Removing Python 2.x support from Django for version 2.0 by Sean1708 on Thursday January 19, 2017 @09:54AM (#13436215)
How should you break backwards compatibility then? This is about as good a solution I can come up with.
[ Parent | on HN ]
Re:Removing Python 2.x support from Django for version 2.0 by stefantalpalaru on Thursday January 19, 2017 @07:08AM (#13435119)
> That's exactly how _not_ to break backwards compatibility.

No, no, no. Backwards compatibility means that there are no breaking changes at all - announced by deprecation warnings or not. Think Linux's public API.

[ Parent | on HN ]