@@ -12,19 +12,18 @@ This release removes the ``configparser`` package as an alias for
1212``ConfigParser `` on Py2 to improve compatibility with the backported
1313`configparser package <https://pypi.python.org/pypi/configparser> `. Previously
1414``python-future `` and the PyPI ``configparser `` backport clashed, causing
15- confusion and various compatibility issues. (Issue #118)
15+ various compatibility issues. (Issue #118)
1616
17- This warrants a new major version number for ``python-future `` because Py2/3
18- code that uses `configparser ` will no longer run on Py2 systems without the
19- `configparser ` backport installed. As an upgrade path, run ``pip install
17+ If your code previously relied on ``configparser `` being supplied by
18+ ``python-future ``, the recommended upgrade path is to run ``pip install
2019configparser `` or add ``configparser `` to your ``requirements.txt `` file.
2120
22- Note that, if you are upgrading ``future `` with ``pip ``, you will need to
21+ Note that, if you are upgrading ``future `` with ``pip ``, you may need to
2322uninstall the old version of future or manually remove the
24- ``site-packages/future-0.15.3.dev0 -py2.7.egg/configparser/ `` folder for this
25- change to take effect on your system.
23+ ``site-packages/future-0.15.2 -py2.7.egg `` folder for this change to take
24+ effect on your system.
2625
27- This releases fixes also these bugs:
26+ This releases also fixes these bugs:
2827
2928- Fix ``newbytes `` constructor bug. (Issue #163)
3029- Fix semantics of `bool() ` with `newobject `. (Issue #211)
0 commit comments