From cfc494e86d7f942fcaf71452be8f2d491591a487 Mon Sep 17 00:00:00 2001 From: Joe Gordon Date: Wed, 7 Nov 2018 16:34:50 -0800 Subject: [PATCH] Update doc/futurize to reflect what gets run Compare rc/libfuturize/fixes/__init__.py and doc/futurize.rst to make sure they align. --- docs/futurize.rst | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/docs/futurize.rst b/docs/futurize.rst index fdbf3026..e7e593c0 100644 --- a/docs/futurize.rst +++ b/docs/futurize.rst @@ -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 @@ -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 @@ -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 @@ -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.