On 25 March 2014 00:36, Nick Coghlan <ncogh...@gmail.com> wrote: > On 25 March 2014 00:18, Skip Montanaro <s...@pobox.com> wrote: > The PEP does not permit backwards compatibility breaks in maintenance > releases
Well, ssl.create_default_context() will use the same "this is a dynamic best practices API" policy as it does in 3.4. But everything that already exists in 2.7.6 will remain compatible with that behaviour by default. The policy change in the PEP won't automagically make networked software secure - it will just make it a heck of a lot *easier* to write in Python 2 (or the common subset of Python 2 and Python 3) by backporting the Python 3.4 enhancements to a 2.7 maintenance release, and, depending on the relative timing of the releases, likely the Python 3.5 enhancements to a later maintenance release. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
