mirror of https://github.com/python/cpython.git
typo corrections (thanks to Paul Taney)
This commit is contained in:
parent
af956f1d48
commit
23681daa71
|
@ -53,14 +53,14 @@ After transformation, :file:`example.py` looks like this::
|
|||
Comments and and exact indentation are preserved throughout the translation
|
||||
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 by use
|
||||
of the :option:`-f` flag. The following example runs only the ``imports`` and
|
||||
By default, 2to3 runs a set of predefined fixers. The :option:`-l` flag lists
|
||||
all available fixers. An explicit set of fixers to run can be given by use of
|
||||
the :option:`-f` flag. The following example runs only the ``imports`` and
|
||||
``has_key`` fixers::
|
||||
|
||||
$ 2to3 -f imports -f has_key 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::
|
||||
|
||||
|
@ -68,7 +68,7 @@ the ``idioms`` fixer is run::
|
|||
|
||||
Notice how passing ``all`` enables all default fixers.
|
||||
|
||||
Sometimes 2to3 will find will find a place in your source code that needs to be
|
||||
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.
|
||||
|
@ -81,12 +81,12 @@ document could also be refactored with this option.
|
|||
The :option:`-v` option enables the output of more information on the
|
||||
translation process.
|
||||
|
||||
When the :option:`-p` is passed, 2to3 treats ``print`` as a function instead of
|
||||
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
|
||||
true function call.
|
||||
When the :option:`-p` is passed, 2to3 treats ``print`` as a function instead
|
||||
of 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 print statement with parentheses (such as ``print ("a" + "b" +
|
||||
"c")``) and a true function call.
|
||||
|
||||
|
||||
:mod:`lib2to3` - 2to3's library
|
||||
|
|
Loading…
Reference in New Issue