Commit dfe4e3aa authored by Agustin Henze's avatar Agustin Henze

New upstream version 3.5.0b2

parent 314034af
Metadata-Version: 1.1
Name: configparser
Version: 3.5.0
Version: 3.5.0b2
Summary: This library brings the updated configparser from Python 3.5 to Python 2.6-3.5.
Home-page: http://docs.python.org/3/library/configparser.html
Author: Łukasz Langa
......@@ -157,7 +157,8 @@ Description: ============
2.6 - 3.5. To use on Python 3 import ``from backports import configparser``
instead of the built-in version.
* compatible with 3.5.1
* compatible with 3.4.1 + fixes for `#19546
<http://bugs.python.org/issue19546>`_
* fixes `BitBucket issue #1
<https://bitbucket.org/ambv/configparser/issue/1>`_: versioning non-compliant
......@@ -264,20 +265,15 @@ Description: ============
The process works like this:
1. I update the ``3.x`` branch with new versions of files. Note that the
actual ``configparser.py`` file is now just a proxy for sources held in
``backports/configparser/__init__.py``.
1. I update the ``3.x`` branch with new versions of files. Commit.
2. I check for new names in ``__all__`` and update imports in
``configparser.py`` accordingly. I run the tests on Python 3. Commit.
2. I merge the new commit to ``default``. I run ``tox``. Commit.
3. I merge the new commit to ``default``. I run ``tox``. Commit.
4. If there are necessary changes, I do them now (on ``default``). Note that
3. If there are necessary changes, I do them now (on ``default``). Note that
the changes should be written in the syntax subset supported by Python
2.6.
5. I run ``tox``. If it works, I update the docs and release the new version.
4. I run ``tox``. If it works, I update the docs and release the new version.
Otherwise, I go back to point 3. I might use ``pasteurize`` to suggest me
required changes but usually I do them manually to keep resulting code in
a nicer form.
......@@ -322,7 +318,8 @@ Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.2
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Software Development :: Libraries :: Python Modules
......@@ -149,7 +149,8 @@ Change Log
2.6 - 3.5. To use on Python 3 import ``from backports import configparser``
instead of the built-in version.
* compatible with 3.5.1
* compatible with 3.4.1 + fixes for `#19546
<http://bugs.python.org/issue19546>`_
* fixes `BitBucket issue #1
<https://bitbucket.org/ambv/configparser/issue/1>`_: versioning non-compliant
......@@ -256,20 +257,15 @@ conversion was not doable, I took the following branching approach:
The process works like this:
1. I update the ``3.x`` branch with new versions of files. Note that the
actual ``configparser.py`` file is now just a proxy for sources held in
``backports/configparser/__init__.py``.
1. I update the ``3.x`` branch with new versions of files. Commit.
2. I check for new names in ``__all__`` and update imports in
``configparser.py`` accordingly. I run the tests on Python 3. Commit.
2. I merge the new commit to ``default``. I run ``tox``. Commit.
3. I merge the new commit to ``default``. I run ``tox``. Commit.
4. If there are necessary changes, I do them now (on ``default``). Note that
3. If there are necessary changes, I do them now (on ``default``). Note that
the changes should be written in the syntax subset supported by Python
2.6.
5. I run ``tox``. If it works, I update the docs and release the new version.
4. I run ``tox``. If it works, I update the docs and release the new version.
Otherwise, I go back to point 3. I might use ``pasteurize`` to suggest me
required changes but usually I do them manually to keep resulting code in
a nicer form.
......
......@@ -30,7 +30,7 @@ else:
setup(
name='configparser',
version='3.5.0',
version='3.5.0b2',
author=author,
author_email='lukasz@langa.pl',
description=__doc__,
......@@ -57,8 +57,9 @@ setup(
'Programming Language :: Python :: 2.6',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.2',
'Programming Language :: Python :: 3.3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Topic :: Software Development :: Libraries',
'Topic :: Software Development :: Libraries :: Python Modules',
],
......
This diff is collapsed.
Metadata-Version: 1.1
Name: configparser
Version: 3.5.0
Version: 3.5.0b2
Summary: This library brings the updated configparser from Python 3.5 to Python 2.6-3.5.
Home-page: http://docs.python.org/3/library/configparser.html
Author: Łukasz Langa
......@@ -157,7 +157,8 @@ Description: ============
2.6 - 3.5. To use on Python 3 import ``from backports import configparser``
instead of the built-in version.
* compatible with 3.5.1
* compatible with 3.4.1 + fixes for `#19546
<http://bugs.python.org/issue19546>`_
* fixes `BitBucket issue #1
<https://bitbucket.org/ambv/configparser/issue/1>`_: versioning non-compliant
......@@ -264,20 +265,15 @@ Description: ============
The process works like this:
1. I update the ``3.x`` branch with new versions of files. Note that the
actual ``configparser.py`` file is now just a proxy for sources held in
``backports/configparser/__init__.py``.
1. I update the ``3.x`` branch with new versions of files. Commit.
2. I check for new names in ``__all__`` and update imports in
``configparser.py`` accordingly. I run the tests on Python 3. Commit.
2. I merge the new commit to ``default``. I run ``tox``. Commit.
3. I merge the new commit to ``default``. I run ``tox``. Commit.
4. If there are necessary changes, I do them now (on ``default``). Note that
3. If there are necessary changes, I do them now (on ``default``). Note that
the changes should be written in the syntax subset supported by Python
2.6.
5. I run ``tox``. If it works, I update the docs and release the new version.
4. I run ``tox``. If it works, I update the docs and release the new version.
Otherwise, I go back to point 3. I might use ``pasteurize`` to suggest me
required changes but usually I do them manually to keep resulting code in
a nicer form.
......@@ -322,7 +318,8 @@ Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.2
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Software Development :: Libraries :: Python Modules
......@@ -31,7 +31,6 @@ from backports.configparser import (
InterpolationDepthError,
ParsingError,
MissingSectionHeaderError,
ConverterMapping,
_UNSET,
DEFAULTSECT,
......@@ -39,14 +38,3 @@ from backports.configparser import (
_default_dict,
_ChainMap,
)
__all__ = ["NoSectionError", "DuplicateOptionError", "DuplicateSectionError",
"NoOptionError", "InterpolationError", "InterpolationDepthError",
"InterpolationMissingOptionError", "InterpolationSyntaxError",
"ParsingError", "MissingSectionHeaderError",
"ConfigParser", "SafeConfigParser", "RawConfigParser",
"Interpolation", "BasicInterpolation", "ExtendedInterpolation",
"LegacyInterpolation", "SectionProxy", "ConverterMapping",
"DEFAULTSECT", "MAX_INTERPOLATION_DEPTH"]
# NOTE: names missing from __all__ imported anyway for backwards compatibility.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment