PEP 469 wording tweaks
This commit is contained in:
parent
a4808c9af9
commit
02a84a7e36
|
@ -77,7 +77,7 @@ those semantics get a free memory efficiency improvement when migrating to
|
|||
Python 3, and face no additional difficulties when migrating via the common
|
||||
subset of Python 2 and 3.
|
||||
|
||||
By contrast, users that actually want the increased efficiency will have
|
||||
By contrast, users that actually want the increased efficiency may have
|
||||
faced a three phase migration process by the time they have fully migrated
|
||||
to Python 3:
|
||||
|
||||
|
@ -85,8 +85,8 @@ to Python 3:
|
|||
Python 2.2
|
||||
* migration to a separate function based API in order to run in the common
|
||||
subset of Python 2 and 3
|
||||
* eventual migration back to unprefixed method APIs when eventually dropping
|
||||
Python 2.7 support
|
||||
* eventual migration back to unprefixed method APIs when finally dropping
|
||||
Python 2.7 support at some point in the future
|
||||
|
||||
The view based APIs that were added to Python 2.7 don't actually help with
|
||||
the transition process, as they don't exist in Python 3 and hence aren't
|
||||
|
|
Loading…
Reference in New Issue