On Tue, 2 Sep 2014 16:47:35 -0700 Glyph Lefkowitz email@example.com wrote:
On Sep 2, 2014, at 4:28 PM, Nick Coghlan firstname.lastname@example.org wrote:
On 3 Sep 2014 09:08, "David Reid" email@example.com 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.