PEP 493: formatting & wording tweaks
This commit is contained in:
parent
14466c2300
commit
52973f08f9
20
pep-0493.txt
20
pep-0493.txt
|
@ -20,10 +20,8 @@ This PEP provides recommendations to downstream redistributors wishing to
|
||||||
provide a smoother migration experience when helping their users to manage
|
provide a smoother migration experience when helping their users to manage
|
||||||
this change in Python's default behaviour.
|
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
|
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
|
new settings process wide by monkeypatching the ``ssl`` module to restore the
|
||||||
old behaviour. Unfortunately, the ``sitecustomize.py`` based technique proposed
|
old behaviour. Unfortunately, the ``sitecustomize.py`` based technique proposed
|
||||||
to allow system administrators to disable the feature by default in their
|
to allow system administrators to disable the feature by default in their
|
||||||
Standard Operating Environment definition has been determined not to work in
|
Standard Operating Environment definition has been determined to be
|
||||||
at least some cases. The specific case of interest to the authors of this PEP
|
insufficient in at least some cases. The specific case of interest to the
|
||||||
is the one where a commercial redistributor aims to provide their users with a
|
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>`__
|
`smoother migration path <https://bugzilla.redhat.com/show_bug.cgi?id=1173041>`__
|
||||||
than the standard one provided by consuming the upstream CPython 2.7
|
than the standard one provided by consuming upstream CPython 2.7 releases
|
||||||
distribution directly, but other potential challenges have also been pointed
|
directly, but other potential challenges have also been pointed out with
|
||||||
out with updating embedded Python runtimes and other user level installations
|
updating embedded Python runtimes and other user level installations of Python.
|
||||||
of Python.
|
|
||||||
|
|
||||||
Rather than allowing a plethora of mutually incompatibile migration techniques
|
Rather than allowing a plethora of mutually incompatibile migration techniques
|
||||||
to bloom, this PEP proposes two alternative approaches that redistributors
|
to bloom, this PEP proposes two alternative approaches that redistributors
|
||||||
|
|
Loading…
Reference in New Issue