26 Mar
2014
26 Mar
'14
4 a.m.
Am 25.03.2014 23:15, schrieb Nick Coghlan:
As long as we make it clear we have chosen to change our backwards-compatibility guarantees in the name of security and have a link to
On 26 Mar 2014 01:19, "Brett Cannon"
mailto:bcannon@gmail.com> wrote: the last backwards-compatible release then I agree as well. I am not sure how this meme got started, but let me be clear: the proposed policy DOES NOT provide blanket permission to break backwards compatibility in the affected modules. It only allows ADDING new features to bring these modules into line with their Python 3 counterparts, making it easier for third party packages like requests to do the right thing in a cross-version compatible way.
We know. That's what we mean by that. Georg