On Mar 25, 2014, at 1:16 PM, Guido van Rossum <gu...@python.org> wrote:
> On Tue, Mar 25, 2014 at 9:46 AM, Donald Stufft <don...@stufft.io> wrote: > > On Mar 25, 2014, at 12:35 PM, Guido van Rossum <gu...@python.org> wrote: > [...] >> >> I do note that the PEP seems to have some weasel-words about breaking >> backward compatibility in the name of security. The phrase "This PEP does >> not grant Python 2.7 any general exemptions to the usual backwards >> compatibility policy for maintenance releases" *could* be interpreted to >> imply that the PEP grants some specific exemptions (regardless of whether >> that was Nick's intention when he wrote that sentence). I'd like clarity on >> this; IIRC we've had to make some compatibility-breaking changes in the past >> for security reasons, but I don't recall the details or how that worked out >> (whether much code broke and whether that was considered a good or a bad >> thing). > > I’m pretty sure Nick was just trying to say that the changes made under this > PEP still have to be backwards compatible in the sense that APIs can’t change > their default behavior and such. In other words we can’t suddenly flip on > hostname checking or anything like that. > > Then the words should be clarified (maybe by removing 'general'?). This PEP > invites interpretation by future generations so it should be as clear as > possible on the intent, to avoid scholarly arguments. > > -- > --Guido van Rossum (python.org/~guido) Yea I agree, was just stating what I understand the PEP to be proposing :) ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
