RetroSearch Browse

Mon Mar 24 15:40:59 CET 2014 · http://mail.python.org/pipermail/python-dev/2014-March/133448.html

On 25 March 2014 00:36, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 25 March 2014 00:18, Skip Montanaro <skip at 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   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2014-March/133448.html below:

[Python-Dev] PEP 466: Proposed policy change for handling network security enhancements