futurize: move exec fixer to stage1

Author: edschofield

docs/whatsnew.rst

@@ -5,6 +5,12 @@ What's New
 
 .. _whats-new-0.15.x:
 
+What's new in version 0.15.1 (in development)
+=============================================
+
+- ``futurize``: Moved exec fixer to stage1. The forward-compatible ``exec(a, b)`` idiom is supported in Python 2.6 and 2.7. See https://docs.python.org/2/reference/simple_stmts.html#exec.
+
+
 What's new in version 0.15.0 (2015-07-25)
 =========================================
 

src/libfuturize/fixes/__init__.py

@@ -8,6 +8,7 @@
 lib2to3_fix_names_stage1 = set([
     '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',
@@ -43,7 +44,6 @@
     # 'lib2to3.fixes.fix_buffer',    # perhaps not safe. Test this.
     # 'lib2to3.fixes.fix_callable',  # not needed in Py3.2+
     'lib2to3.fixes.fix_dict',        # TODO: add support for utils.viewitems() etc. and move to stage2
-    'lib2to3.fixes.fix_exec',
     # 'lib2to3.fixes.fix_execfile',  # some problems: see issue #37.
                                      # We use a custom fixer instead (see below)
     # 'lib2to3.fixes.fix_future',    # we don't want to remove __future__ imports