iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 493: formatting & wording tweaks

This commit is contained in:
Nick Coghlan 2015-05-13 00:08:31 +10:00
parent 14466c2300
commit 52973f08f9
1 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
pep-0493.txt
View File

@ -20,10 +20,8 @@ This PEP provides recommendations to downstream redistributors wishing to
provide a smoother migration experience when helping their users to manage
this change in Python's default behaviour.
.. note::
Note that this PEP is not currently accepted, so it is a *proposed*
recommendation, rather than an active one.
*Note that this PEP is not currently accepted, so it is a *proposed*
recommendation, rather than an active one.*
Rationale
=========
@ -49,14 +47,14 @@ PEP 476 did attempt to address this question, by covering how to revert the
new settings process wide by monkeypatching the ``ssl`` module to restore the
old behaviour. Unfortunately, the ``sitecustomize.py`` based technique proposed
to allow system administrators to disable the feature by default in their
Standard Operating Environment definition has been determined not to work in
at least some cases. The specific case of interest to the authors of this PEP
is the one where a commercial redistributor aims to provide their users with a
Standard Operating Environment definition has been determined to be
insufficient in at least some cases. The specific case of interest to the
authors of this PEP is the one where a Linux distributor aims to provide
their users with a
`smoother migration path <https://bugzilla.redhat.com/show_bug.cgi?id=1173041>`__
than the standard one provided by consuming the upstream CPython 2.7
distribution directly, but other potential challenges have also been pointed
out with updating embedded Python runtimes and other user level installations
of Python.
than the standard one provided by consuming upstream CPython 2.7 releases
directly, but other potential challenges have also been pointed out with
updating embedded Python runtimes and other user level installations of Python.
Rather than allowing a plethora of mutually incompatibile migration techniques
to bloom, this PEP proposes two alternative approaches that redistributors