Skip to main content
https://img.shields.io/pypi/v/configparser.svg https://img.shields.io/pypi/pyversions/configparser.svg tests Ruff https://readthedocs.org/projects/configparser/badge/?version=latest https://img.shields.io/badge/skeleton-2024-informational https://tidelift.com/badges/package/pypi/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 http://docs.python.org/3/library/configparser.html.

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:

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.

Metadata

Release files for configparser 7.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for configparser 7.0.0
File Size Uploaded Provenance Actions
configparser-7.0.0.tar.gz 49.9 kB Without provenance Details for configparser-7.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for configparser 7.0.0
File Interpreter ABI Platform Actions
configparser-7.0.0-py3-none-any.whl Python 3 none any Details for configparser-7.0.0-py3-none-any.whl

Total release size: 66.9 kB

Release files / configparser-7.0.0.tar.gz

Download URL configparser-7.0.0.tar.gz
Size 49.9 kB
Tags Source
SHA-256 checksum
How to use checksums
af3c618a67aaaedc4d689fd7317d238f566b9aa03cae50102e92d7f0dfe78ba0
BLAKE2b-256 checksum
How to use checksums
fd1da0f55c373f80437607b898956518443b9edd435b5a226392a9ef11d79fa0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.12.2

Release files / configparser-7.0.0-py3-none-any.whl

Download URL configparser-7.0.0-py3-none-any.whl
Size 17.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f46d52a12811c637104c6bb8eb33693be0038ab6bf01d69aae009c39ec8c2017
BLAKE2b-256 checksum
How to use checksums
a820f4aab9a42378542295c3be2bbdab353de10eb95396f6d4a5bc7a21b00952
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.0.0 CPython/3.12.2

Security for configparser 7.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

7.0.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page