[Python-checkins] r66998 - python/trunk/Doc/library/2to3.rst

benjamin.peterson python-checkins at python.org
Wed Oct 22 22:57:44 CEST 2008


Author: benjamin.peterson
Date: Wed Oct 22 22:57:43 2008
New Revision: 66998

Log:
fix a few typos

Modified:
   python/trunk/Doc/library/2to3.rst

Modified: python/trunk/Doc/library/2to3.rst
==============================================================================
--- python/trunk/Doc/library/2to3.rst	(original)
+++ python/trunk/Doc/library/2to3.rst	Wed Oct 22 22:57:43 2008
@@ -54,7 +54,7 @@
 process.
 
 By default, 2to3 runs a set of predefined fixers.  The :option:`-l` flag lists
-all avaible fixers.  An explicit set of fixers to run can be given with
+all available fixers.  An explicit set of fixers to run can be given with
 :option:`-f`.  Likewise the :option:`-x` explicitly disables a fixer.  The
 following example runs only the ``imports`` and ``has_key`` fixers::
 
@@ -64,7 +64,7 @@
 
    $ 2to3 -x apply example.py
 
-Some fixers are *explicit*, meaning they aren't run be default and must be
+Some fixers are *explicit*, meaning they aren't run by default and must be
 listed on the command line to be run.  Here, in addition to the default fixers,
 the ``idioms`` fixer is run::
 
@@ -72,10 +72,10 @@
 
 Notice how passing ``all`` enables all default fixers.
 
-Sometimes 2to3 will find will find a place in your source code that needs to be
-changed, but 2to3 cannot fix automatically.  In this case, 2to3 will print a
-warning beneath the diff for a file.  You should address the warning in order to
-have compliant 3.x code.
+Sometimes 2to3 will find a place in your source code that needs to be changed,
+but 2to3 cannot fix automatically.  In this case, 2to3 will print a warning
+beneath the diff for a file.  You should address the warning in order to have
+compliant 3.x code.
 
 2to3 can also refactor doctests.  To enable this mode, use the :option:`-d`
 flag.  Note that *only* doctests will be refactored.  This also doesn't require
@@ -89,7 +89,7 @@
 a statement.  This is useful when ``from __future__ import print_function`` is
 being used.  If this option is not given, the print fixer will surround print
 calls in an extra set of parentheses because it cannot differentiate between the
-and print statement with parentheses (such as ``print ("a" + "b" + "c")``) and a
+print statement with parentheses (such as ``print ("a" + "b" + "c")``) and a
 true function call.
 
 


More information about the Python-checkins mailing list