On Tue, 2 Sep 2014 16:47:35 -0700 Glyph Lefkowitz <glyph at twistedmatrix.com> wrote: > > On Sep 2, 2014, at 4:28 PM, Nick Coghlan <ncoghlan at gmail.com> wrote: > > > On 3 Sep 2014 09:08, "David Reid" <dreid at dreid.org> wrote: > > > > > > Nick Coghlan <ncoghlan <at> gmail.com> writes: > > > > > > > Creating *new* incompatibilities between Python 2 & Python 3 is a major point > > > > of concern. > > > > > > Clearly this change should be backported to Python2. > > > > Proposing to break backwards compatibility in a maintenance release (...) > > > > As we keep saying, this is not a break in backwards compatibility, it's a bug fix. Keeping saying it doesn't make it magically true. Besides, it can perfectly well be a bug fix *as well as* a break in backwards compatibility. Which is why we sometimes choose to fix bugs only in the feature development branch. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4