Skip to content

Update doc/futurize to reflect what gets run #413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2019
Merged

Update doc/futurize to reflect what gets run #413

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions docs/futurize.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,7 @@ The complete set of fixers applied by ``futurize --stage1`` is:

lib2to3.fixes.fix_apply
lib2to3.fixes.fix_except
lib2to3.fixes.fix_exec
lib2to3.fixes.fix_exitfunc
lib2to3.fixes.fix_funcattrs
lib2to3.fixes.fix_has_key
Expand Down Expand Up @@ -224,9 +225,7 @@ becomes::

The complete list of fixers applied in Stage 2 is::

lib2to3.fixes.fix_basestring
lib2to3.fixes.fix_dict
lib2to3.fixes.fix_exec
lib2to3.fixes.fix_getcwdu
lib2to3.fixes.fix_input
lib2to3.fixes.fix_itertools
Expand All @@ -239,8 +238,9 @@ The complete list of fixers applied in Stage 2 is::
lib2to3.fixes.fix_raw_input
lib2to3.fixes.fix_zip

libfuturize.fixes.fix_basestring
libfuturize.fixes.fix_cmp
libfuturize.fixes.fix_division
libfuturize.fixes.fix_division_safe
libfuturize.fixes.fix_execfile
libfuturize.fixes.fix_future_builtins
libfuturize.fixes.fix_future_standard_library
Expand Down Expand Up @@ -269,11 +269,6 @@ Not applied::
lib2to3.fixes.fix_xrange # Custom one because of a bug with Py3.3's lib2to3


Fixes applied with the ``futurize --conservative`` option::

libfuturize.fixes.fix_division_safe # instead of libfuturize.fixes.fix_division.



.. Ideally the output of this stage should not be a ``SyntaxError`` on either
.. Python 3 or Python 2.
Expand Down