To help you get started, we've collected the most common ways that configparser is being used within popular public projects.

Python-Markdown / markdown / tests / util.py View on Github

def get(self, section, option):
        value = ConfigParser.get(self, section, option)
        if option == 'extensions':
            if len(value.strip()):
                return value.split(',')
            else:
                return []
        if value.lower() in ['yes', 'true', 'on', '1']:
            return True
        if value.lower() in ['no', 'false', 'off', '0']:
            return False
        return value

View more ways to use configparser

This package is a backport of the refreshed and enhanced ConfigParser from later Python versions. To use the backport instead of the built-in version, simply import it explicitly as a backport:

from backports import configparser

For detailed documentation consult the vanilla version at .

Versioning

This project uses semver to communicate the impact of various releases while periodically syncing with the upstream implementation in CPython. The history serves as a reference indicating which versions incorporate which upstream functionality.

Prior to the 4.0.0 release, another scheme was used to associate the CPython and backports releases.

Maintenance

This backport was originally authored by Łukasz Langa, the current vanilla configparser maintainer for CPython and is currently maintained by Jason R. Coombs:

• configparser repository
• configparser issue tracker

Conversion Process

This section is technical and should bother you only if you are wondering how this backport is produced. If the implementation details of this backport are not important for you, feel free to ignore the following content.

The project takes the following branching approach:

• The cpython branch holds unchanged files synchronized from the upstream CPython repository. The synchronization is currently done by manually copying the required files and stating from which CPython changeset they come.
• The main branch holds a version of the cpython code with some tweaks that make it compatible with older Pythons. Code on this branch must work on all supported Python versions. Test with tox or in CI.

The process works like this:

1. In the cpython branch, run ./sync-upstream, which downloads the latest stable release of Python and copies the relevant files from there into their new locations and then commits those changes with a nice reference to the relevant upstream commit hash.
2. Merge the new commit to main.
3. Check for new names in __all__ and update imports in configparser/__init__.py accordingly. Run tests. Commit.
4. Make any compatibility changes on main. Run tests. Commit.
5. Update the docs and release the new version.

For Enterprise

Available as part of the Tidelift Subscription.

This project and the maintainers of thousands of other packages are working with Tidelift to deliver one enterprise subscription that covers all of the open source you use.

Learn more.