[Python-checkins] peps: More minor cleanups to PEP 414

nick.coghlan python-checkins at python.org
Sun Mar 4 08:56:27 CET 2012


http://hg.python.org/peps/rev/2dd168f93bfa
changeset:   4108:2dd168f93bfa
user:        Nick Coghlan <ncoghlan at gmail.com>
date:        Sun Mar 04 17:56:12 2012 +1000
summary:
  More minor cleanups to PEP 414

files:
  pep-0414.txt |  18 ++++++++++--------
  1 files changed, 10 insertions(+), 8 deletions(-)


diff --git a/pep-0414.txt b/pep-0414.txt
--- a/pep-0414.txt
+++ b/pep-0414.txt
@@ -221,8 +221,8 @@
 
 Native strings are a useful concept because there are some APIs and internal
 operations that are designed primarily to work with native strings. They often
-don't support ``unicode`` in Python 2 and don't support ``bytes`` in Python 3
-(at least, not without needing additional encoding information and/or imposing
+don't support ``unicode`` in Python 2 or support ``bytes`` in Python 3 (at
+least, not without needing additional encoding information and/or imposing
 constraints that don't apply to the native string variants).
 
 Some example of such interfaces are:
@@ -329,7 +329,7 @@
 across the entire project at the same time, then the meaning of a bare string
 literal may become annoyingly ambiguous. This problem can be particularly
 pernicious for *aggregated* software, like a Django site - in such a situation,
-some files may end up using the unicode literals import and others may not,
+some files may end up using the ``unicode_literals`` import and others may not,
 creating definite potential for confusion.
 
 While these problems are clearly solvable at a technical level, they're a
@@ -342,13 +342,15 @@
 
 Armin Ronacher has created an experimental extension to 2to3 which only
 modernizes Python code to the extent that it runs on Python 2.7 or later with
-support from the cross-version compatibility ``six`` library is available as
-``python-modernize`` [1]_. Currently, the deltas generated by this tool will
-affect every Unicode literal in the converted source. This will create
-legitimate concerns amongst upstream developers asked to accept such changes.
+support from the cross-version compatibility ``six`` library. This tool is
+available as ``python-modernize`` [1]_. Currently, the deltas generated by
+this tool will affect every Unicode literal in the converted source. This
+will create legitimate concerns amongst upstream developers asked to accept
+such changes, and amongst framework *users* being asked to change their
+applications.
 
 However, by eliminating the noise from changes to the Unicode literal syntax,
-many projects could be cleanly and (relatively) non-controversially made
+many projects could be cleanly and (comparatively) non-controversially made
 forward compatible with Python 3.3+ just by running ``python-modernize`` and
 applying the recommended changes.
 

-- 
Repository URL: http://hg.python.org/peps


More information about the Python-checkins mailing list