Remove configparser alias package (issue #118)

Author: edschofield

docs/compatible_idioms.rst

@@ -1413,7 +1413,7 @@ configparser
     # Python 2 only:
     from ConfigParser import ConfigParser
     
-    # Python 2 and 3 (after ``pip install future``):
+    # Python 2 and 3 (after ``pip install configparser``):
     from configparser import ConfigParser
 queue
 ~~~~~

docs/pasteurize.rst

@@ -6,6 +6,7 @@
 Running ``pasteurize -w mypy3module.py`` turns this Python 3 code::
     
     import configparser
+    import copyreg
     
     class Blah:
         pass
@@ -18,6 +19,7 @@ into this code which runs on both Py2 and Py3::
     standard_library.install_hooks()
     
     import configparser
+    import copyreg
 
     class Blah(object):
         pass
@@ -27,6 +29,13 @@ Notice that both ``futurize`` and ``pasteurize`` create explicit new-style
 classes that inherit from ``object`` on both Python versions, and both 
 refer to stdlib modules (as well as builtins) under their Py3 names.
 
+Note also that the ``configparser`` module is a special case; there is a full
+backport available on PyPI (https://pypi.python.org/pypi/configparser), so, as
+of v0.18.0, ``python-future`` no longer provides a ``configparser`` package
+alias. To use the resulting code on Py2, install the ``configparser`` backport
+with ``pip install configparser`` or by adding it to your ``requirements.txt``
+file.
+
 ``pasteurize`` also handles the following Python 3 features:
 
 - keyword-only arguments
@@ -36,4 +45,3 @@ refer to stdlib modules (as well as builtins) under their Py3 names.
 To handle function annotations (PEP 3107), see :ref:`func_annotations`.
 
 
-

docs/quickstart.rst

@@ -100,7 +100,6 @@ to be accessed under their Python 3 names and locations in Python 2::
     # Then these Py3-style imports work on both Python 2 and Python 3:
     import socketserver
     import queue
-    import configparser
     from collections import UserDict, UserList, UserString
     from collections import Counter, OrderedDict, ChainMap   # even on Py2.6
     from itertools import filterfalse, zip_longest

docs/standard_library_imports.rst

@@ -24,22 +24,20 @@ Python 3 code runs unchanged on Python 2 after installing ``future``::
 
     >>> # Top-level packages with Py3 names provided on Py2:
     >>> import queue
-    >>> import configparser
     >>> import tkinter.dialog
     >>> etc.
 
 Notice that this code actually runs on Python 3 without the presence of the
 ``future`` package.
 
 Of the 44 modules that were refactored with PEP 3108 (standard library
-reorganization), 30 are supported with direct imports in the above manner. The
+reorganization), 29 are supported with direct imports in the above manner. The
 complete list is here::
 
     ### Renamed modules:
 
     import builtins
 
-    import configparser
     import copyreg
 
     import html
@@ -79,6 +77,8 @@ complete list is here::
     import _markupbase
     import _thread
 
+Note that, as of v0.18.0, ``python-future`` no longer includes an alias for the
+``configparser`` module because a full backport exists (see https://pypi.python.org/pypi/configparser). 
 
 .. _list-standard-library-refactored:
 

docs/whatsnew.rst

@@ -3,15 +3,30 @@
 What's New
 **********
 
-.. _whats-new-0.15.x:
+.. _whats-new-0.16.x:
 
-What's new in version 0.15.3 (2015-02-...)
+What's new in version 0.16.0 (2016-05-...)
 ==========================================
 
-This is a minor bug-fix release:
-
-- Fix ``newbytes`` constructor bug (issue #163)
-
+This release removes the ``configparser`` package as an alias for
+``ConfigParser`` on Py2 to improve compatibility with the backported
+`configparser package <https://pypi.python.org/pypi/configparser>`. Previously
+``python-future`` and the PyPI ``configparser`` backport clashed, causing
+confusion and various compatibility issues. (Issue #118)
+
+This warrants a new major version number for ``python-future`` because Py2/3
+code that uses `configparser` will no longer run on Py2 systems without the
+`configparser` backport installed. As an upgrade path, run ``pip install
+configparser`` or add ``configparser`` to your ``requirements.txt`` file.
+
+This releases fixes these bugs:
+
+- Fix ``newbytes`` constructor bug. (Issue #163)
+- Fix semantics of `bool()` with `newobject`. (Issue #211)
+- Fix `standard_library.install_aliases()` on PyPy. (Issue #205)
+- Fix assertRaises for `pow` and `compile` on Python 3.5. (Issue #183)
+- Fix return argument of `future.utils.ensure_new_type` if conversion to new type does not exist. (Issue #185)
+- Allow the `old_div` fixer to be disabled. (Issue #190)
 
 What's new in version 0.15.2 (2015-09-11)
 =========================================

setup.py

@@ -58,7 +58,7 @@
 if sys.version_info[:2] < (3, 0):
     PACKAGES += [
             "builtins",
-            "configparser",
+            # "configparser",  # removed in v0.18.0
             "copyreg",
             "html",
             "http",
@@ -125,7 +125,7 @@
     # If the user happens to run:
     #     python2 setup.py build
     #     python3 setup.py install
-    # then folders like "configparser" will be in build/lib.
+    # then folders like "copyreg" will be in build/lib.
     # If so, we CANNOT let the user install this, because
     # this may break his/her Python 3 install, depending on the folder order in
     # sys.path. (Running "import configparser" etc. may pick up our Py2
@@ -135,7 +135,7 @@
                           '_markupbase',
                           '_thread',
                           'builtins',
-                          'configparser',
+                          # 'configparser',
                           'copyreg',
                           'html',
                           'http',

src/configparser/__init__.py

@@ -31,7 +31,6 @@
 following Py3 interfaces:
 
     >>> # Top-level packages with Py3 names provided on Py2:
-    >>> import configparser
     >>> import html.parser
     >>> import queue
     >>> import tkinter.dialog

src/future/__init__.py

@@ -11,7 +11,6 @@
 And then these normal Py3 imports work on both Py3 and Py2::
 
     import builtins
-    import configparser
     import copyreg
     import queue
     import reprlib
@@ -739,8 +738,9 @@ class exclude_local_folder_imports(object):
     A context-manager that prevents standard library modules like configparser
     from being imported from the local python-future source folder on Py3.
 
-    (The presence of a configparser folder would otherwise prevent setuptools
-    from running on Py3.)
+    (This was need prior to v0.18.0 because the presence of a configparser
+    folder would otherwise have prevented setuptools from running on Py3. Maybe
+    it's not needed any more?)
     """
     def __init__(self, *args):
         assert len(args) > 0

src/future/standard_library/__init__.py

@@ -631,7 +631,9 @@ def test_renamed_modules(self):
         import pickle
         import io
         """
-        self.convert_check(before, after)
+        # We can't run the converted code because configparser may
+        # not be there.
+        self.convert_check(before, after, run=False)
 
     @unittest.skip('Not working yet ...')
     def test_urllib_refactor(self):