ConfigUpdater 3.2__tar.gz → 4.0__tar.gz

configupdater-4.0/.gitignore

@@ -0,0 +1,59 @@
+# Byte-compiled files and caches
+__pycache__/
+*.py[cod]
+*.so
+.cache/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+
+# Virtual environments
+.venv*/
+.conda*/
+.tox/
+.python-version
+
+# Build artifacts
+build/
+dist/
+*.egg-info/
+*.egg
+.eggs/
+
+# Coverage and test reports
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+coverage.lcov
+junit*.xml
+
+# Docs
+docs/_build/
+docs/api/
+docs/_rst/
+docs/html/
+site/
+
+# Editors and OS files
+.idea/
+.vscode/
+.project
+.pydevproject
+.settings/
+.ropeproject
+tags
+*~
+.*.swp
+.DS_Store
+*/.ipynb_checkpoints/
+
+# Claude Code (local only)
+.claude/worktrees/
+.claude/settings.local.json
+
+# Temporary files
+*.orig
+*.bak
+*.log
+*.pot

{ConfigUpdater-3.2 → configupdater-4.0}/AUTHORS.rst

@@ -3,5 +3,10 @@ Contributors
 ============
 
 * Florian Wilhelm <florian.wilhelm@gmail.com>
-* Christian Theune <ct@flyingcircus.io>
 * Anderson Bravalheri <andersonbravalheri@gmail.com>
+* Christian Theune <ct@flyingcircus.io>
+* codeofwxz (GitHub)
+* mika <211269698+mikamikasuki@users.noreply.github.com>
+* Sinkleberg
+* blouirts123 (GitHub)
+* bysiber (GitHub)

configupdater-4.0/CHANGELOG.rst

@@ -0,0 +1,183 @@
+=========
+Changelog
+=========
+
+Version 4.0
+===========
+
+- **Breaking:** Drop support for Python < 3.11, the minimum supported version is now
+  Python 3.11, PR #150
+- Add support for Python 3.15, PR #160
+- Simplify type hints using Python 3.11 features (``typing.Self``, ``X | Y`` unions)
+  and remove compatibility code for older Python versions, PR #150
+- Add ``add_before_skip_comments`` to ``Section`` for inserting blocks before the
+  comments that directly precede a section, issue #117
+- Fix ``add_section`` gluing the new section header to the last line when the file
+  does not end with a newline, issue #126
+- Fix ``None`` being written as delimiter when assigning a value to an option that was
+  parsed without a value (``allow_no_value``), issue #141
+- Port the option regexes of Python 3.15's ``configparser`` (CPython gh-146333). The
+  old ones backtracked quadratically, so a long line with many spaces could stall
+  the parser for minutes, PR #161
+- Fix navigating, detaching or inserting at the wrong position when a container holds
+  several equal comment or blank-line blocks, issue #140
+- ``del section[key]`` (and thus ``section.pop(key)``) now applies ``optionxform``
+  like ``section[key]`` does, PR #148
+- Document that a custom ``optionxform`` must be idempotent, PR #152
+- Build with hatchling and hatch-vcs, with all metadata in ``pyproject.toml``. The
+  wheel is now tagged ``py3-none-any`` (instead of ``py2.py3-none-any``), and the
+  license is declared as a PEP 639 expression. The ``testing`` extra is removed;
+  development dependencies are dependency groups, e.g. ``uv sync``, PR #156
+- Complete the type annotations of the public API, now checked with mypy in strict
+  mode, and fix the ``NoneValueDisallowed`` warning under ``python -OO``, PR #158
+- Fix ``NotAttachedError``, ``AlreadyAttachedError`` and ``AssignMultilineValueError``
+  failing with an ``AttributeError`` under ``python -OO``, PR #163
+- Correct the ``NoneValueDisallowed`` message. It claimed that an option without a
+  value is written with an empty value, but the option is omitted since version 3.0.1,
+  PR #163
+- ``add_before.option`` and ``add_after.option`` pass ``delimiter`` and
+  ``space_around_delimiters`` on to the new option instead of silently ignoring all
+  keyword arguments. Other keyword arguments now raise a ``TypeError``, PR #163
+- **Breaking:** An explicit ``space_around_delimiters`` of an ``Option`` (also given
+  to ``add_before.option``, ``add_after.option`` or ``Section.create_option``) now
+  takes precedence over the syntax options of the ``ConfigUpdater``, so ``False``
+  writes ``key=value`` even with the default ``space_around_delimiters=True``.
+  ``Option`` defaults to ``space_around_delimiters=None``, i.e. it follows the
+  ``ConfigUpdater`` it belongs to: ``Option("key", "value")`` now writes
+  ``key=value`` into a ``ConfigUpdater(space_around_delimiters=False)`` instead of
+  ``key = value``. Options created with ``section[key] = value`` or ``set`` keep
+  following the ``ConfigUpdater`` they are copied to, PR #166
+- **Breaking:** ``key in section``, ``section.has_option(key)`` and
+  ``section.get(key)`` now apply ``optionxform`` to ``key``, like ``section[key]``
+  and ConfigParser do. With the default ``str.lower``, ``"KEY" in section`` is now
+  ``True`` and ``section.get("KEY")`` returns the option instead of ``None``, PR #153
+- **Breaking:** ``Section.set`` and ``ConfigUpdater.set`` keep the given spelling
+  when they create a new option, like ``section[key] = value`` does. For example,
+  ``updater.set("metadata", "Name", "x")`` now writes ``Name = x`` instead of
+  ``name = x``, PR #153
+- ``ConfigUpdater.set``, ``get``, ``has_option`` and ``remove_option`` apply
+  ``optionxform`` only once instead of transforming already transformed keys again,
+  PR #153
+- Fix wrong code examples in the usage guide and the README, which are now tested,
+  PR #164
+- Fix ``update_file`` writing the file with the platform's default encoding instead
+  of the encoding it was read with. ``read`` and ``read_file`` remember the encoding
+  (``read_file`` takes it from ``f.encoding``), PR #165
+- ``ConfigUpdater.read`` and ``Parser.read`` call ``io.text_encoding`` like
+  ConfigParser, so with ``-X warn_default_encoding`` the ``EncodingWarning`` points
+  to the caller (PEP 597), PR #165
+
+Version 3.2
+===========
+
+- Option ``prepend_newline`` in ``set_values`` to optionally avoid new lines, issue #104
+- Fix square brackets not parsed in section names, issue #122
+
+Version 3.1.1
+=============
+
+- Preserve indentation of section when there are comments, issue #92
+
+Version 3.1
+===========
+
+- Prevent modifying multi-line values directly with ``value``, issue #87
+- Added ``append`` method to ``Option`` for editing multi-line values
+- Added ``as_list`` method to ``Option`` to handle multi-line values more easily
+
+Version 3.0.1
+=============
+
+- Fix error when parsing unindented comments in multi-line values, issue #73
+- Fix invalid string produced when ``allow_no_value = False``, issue #68
+
+Version 3.0
+===========
+
+- Added type hinting, issue #16
+- Fix parsing error of indented comment lines, issue #25
+- Allow handling of raw section comment, issue #25
+- More unit testing of optionxform, issue #55
+- Allowing sections/options to be copied from one document to the other, issue #47
+- New logo, issue #29
+- Whole API was rechecked by @abravalheri and changed for consistency, issue #19
+
+
+Version 2.0
+===========
+
+- Changes in parser, i.e. comments in multi-line option values are kept
+- Issue #14 is fixed
+- Parameter ``empty_lines_in_values`` is now activated by default and can be changed
+- Renamed ``sections_blocks`` to ``section_blocks`` for consistency
+- Renamed ``last_item`` to ``last_block`` for consistency
+- Added ``first_block``
+- Reworked some internal parts of the inheritance hierarchy
+- Added ``remove`` to remove the current block
+- Added ``next_block`` and ``previous_block`` for easier navigation in section
+
+Version 1.1.3
+=============
+
+- Added fallback option to ConfigUpdater.get reflecting ConfigParser
+
+Version 1.1.2
+=============
+
+- Fix wrongly modifying input in Option.set_value #11
+
+Version 1.1.1
+=============
+
+- Fix iterating over the items() view of a section breaks #8
+
+Version 1.1
+===========
+
+- Validate format on write by default (can be deactivated)
+- Fixed issue #7 with mixed-case options
+- Fixed issue #7 with add_before/add_after problem
+- Fixed issue #7 with wrong duplicate mixed-case entries
+- Fixed issue #7 with duplicate options after add_after/before
+
+Version 1.0.1
+=============
+
+- More sane error message if ``read_file`` is misused
+- Also run unittests with Windows
+
+Version 1.0
+===========
+
+- Fix: Use \n instead of os.linesep where appropriate
+
+Version 0.3.2
+=============
+
+- Added Github and documentation link into the project's metadata
+
+Version 0.3.1
+=============
+
+- Require Python >= 3.4 with ``python_requires``
+
+Version 0.3
+===========
+
+- Added a ``insert_at`` function at section level
+- Some internal code simplifications
+
+Version 0.2
+===========
+
+- Added a ``to_dict()`` function
+
+Version 0.1.1
+=============
+
+- Allow for flexible comment character in ``comment(...)``
+
+Version 0.1
+===========
+
+- First release

{ConfigUpdater-3.2 → configupdater-4.0}/CONTRIBUTING.rst

@@ -22,34 +22,30 @@ additional considerations and avoids unnecessary work.
 Create an environment
 ---------------------
 
-Before you start coding we recommend to install Miniconda_ which allows
-to setup a dedicated development environment named ``configupdater`` with::
-
-   conda create -n configupdater python=3 virtualenv pytest pytest-cov
-
-Then activate the environment ``configupdater`` with::
-
-   source activate configupdater
+ConfigUpdater requires Python 3.11 or newer. The development environment is
+managed with uv_, so install it first. uv also downloads a suitable Python
+version if you don't have one.
 
 Clone the repository
 --------------------
 
-#. `Create a Gitub account`_  if you do not already have one.
+#. `Create a Github account`_  if you do not already have one.
 #. Fork the `project repository`_: click on the *Fork* button near the top of the
    page. This creates a copy of the code under your account on the GitHub server.
 #. Clone this copy to your local disk::
 
     git clone git@github.com:YourLogin/configupdater.git
 
-#. Run ``python setup.py develop`` to install ``configupdater`` into your environment.
+#. Create a virtual environment in ``.venv`` with ``configupdater`` and all
+   development tools (pytest, mypy, tox, pre-commit)::
 
-#. Install ``pre-commit``::
+    uv sync
 
-    pip install pre-commit
-    pre-commit install
+#. Install the ``pre-commit`` hooks::
 
-   PyScaffold project comes with a lot of hooks configured to
-   automatically help the developer to check the code being written.
+    uv run pre-commit install
+
+   The hooks automatically check the code you are writing on every commit.
 
 #. Create a branch to hold your changes::
 
@@ -68,12 +64,16 @@ Clone the repository
 
 #. Please check that your changes don't break any unit tests with::
 
-    python setup.py test
+    uv run tox
+
+   or, for a quick run without coverage, ``uv run pytest``.
 
    Don't forget to also add unit tests in case your contribution
    adds an additional feature and is not just a bugfix.
 
-#. Use `flake8`_ to check your code style.
+#. The ``pre-commit`` hooks check your code style with `ruff`_ on every commit.
+   You can also run them on all files with ``uv run tox -e lint``, and check the
+   type hints with ``uv run tox -e typecheck``.
 #. Add yourself to the list of contributors in ``AUTHORS.rst``.
 #. Go to the web page of your ConfigUpdater fork, and click
    "Create pull request" to send your changes to the maintainers for review.
@@ -83,8 +83,8 @@ Clone the repository
 .. _PyPI: https://pypi.python.org/
 .. _project repository: https://github.com/pyscaffold/configupdater/
 .. _Git: https://git-scm.com/
-.. _Miniconda: https://docs.conda.io/en/latest/miniconda.html
+.. _uv: https://docs.astral.sh/uv/getting-started/installation/
 .. _issue tracker: https://github.com/pyscaffold/configupdater/issues
-.. _Create a Gitub account: https://github.com/join
+.. _Create a Github account: https://github.com/join
 .. _creating a PR: https://help.github.com/articles/creating-a-pull-request/
-.. _flake8: https://flake8.pycqa.org/
+.. _ruff: https://docs.astral.sh/ruff/

configupdater-4.0/PKG-INFO

@@ -0,0 +1,349 @@
+Metadata-Version: 2.5
+Name: ConfigUpdater
+Version: 4.0
+Summary: Parser like ConfigParser but for updating configuration files
+Project-URL: Homepage, https://github.com/pyscaffold/configupdater
+Project-URL: Documentation, https://configupdater.readthedocs.io/
+Project-URL: Source, https://github.com/pyscaffold/configupdater/
+Project-URL: Issues, https://github.com/pyscaffold/configupdater/issues
+Project-URL: Changelog, https://configupdater.readthedocs.io/en/latest/changelog.html
+Project-URL: Download, https://pypi.org/project/configupdater/#files
+Project-URL: Conda-Forge, https://anaconda.org/conda-forge/configupdater
+Author-email: Florian Wilhelm <florian.wilhelm@gmail.com>, Anderson Bravalheri <andersonbravalheri@gmail.com>
+License-Expression: MIT
+License-File: LICENSE.txt
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+<div align="center">
+<img src="https://raw.githubusercontent.com/pyscaffold/configupdater/master/docs/gfx/banner-640x323.png" alt="Configupdater logo" width="500" role="img">
+</div>
+<br/>
+
+|         |                                    |
+|---------|------------------------------------|
+| CI/CD   | [![Tests][Tests-image]][Tests-link] [![Coverage][Coverage-image]][Coverage-link] [![Publish Package][Publish-image]][Publish-link] [![GitHub Sponsors][sponsor-image]][sponsor-link]  |
+| Package | [![PyPI - Version][PyPI_ver-image]][PyPI_ver-link] [![Conda - Version][Conda-image]][Conda-link] [![PyPI - Downloads][PyPI_down-image]][PyPI_down-link] [![PyPI - Python Version][PyPI_py-image]][PyPI_py-link] |
+| Details | [![uv][uv-image]][uv-link] [![Linting - Ruff][ruff-image]][ruff-link] [![test - pytest][pytest-image]][pytest-link] [![Pre-Commit][precommit-image]][precommit-link] [![Types - Mypy][mypy-image]][mypy-link] [![License - MIT][MIT-image]][MIT-link] [![Docs - RTD][rtd-image]][rtd-link] |
+
+The sole purpose of [ConfigUpdater] is to easily
+update an INI config file with no changes to the original file except
+the intended ones. This means comments, the ordering of sections and
+key/value-pairs as wells as their cases are kept as in the original
+file. Thus ConfigUpdater provides complementary functionality to
+Python\'s [ConfigParser], which is primarily meant for reading config
+files and writing *new* ones.
+
+# Features
+
+The key differences to [ConfigParser] are:
+
+- minimal invasive changes in the update configuration file,
+- proper handling of comments,
+- only a single config file can be updated at a time,
+- the original case of sections and keys are kept,
+- control over the position of a new section/key
+
+Following features are **deliberately not** implemented:
+
+- interpolation of values,
+- propagation of parameters from the default section,
+- conversions of values,
+- passing key/value-pairs with `default` argument,
+- non-strict mode allowing duplicate sections and keys.
+
+# Usage
+
+First install the package with either:
+
+```console
+pip install configupdater
+```
+
+or add it to a project managed with [uv]:
+
+```console
+uv add configupdater
+```
+
+or:
+
+```console
+conda install -c conda-forge configupdater
+```
+
+Now we can simply do:
+
+```python
+from configupdater import ConfigUpdater
+
+updater = ConfigUpdater()
+updater.read("setup.cfg")
+```
+
+which would read the file `setup.cfg` that is found in many projects.
+
+To change the value of an existing key we can simply do:
+
+```python
+updater["metadata"]["author"].value = "Alan Turing"
+```
+
+At any point we can print the current state of the configuration file
+with:
+
+```python
+print(updater)
+```
+
+To update the read-in file, with the encoding it was read with, just call
+`updater.update_file()` or `updater.write(open('filename','w'))` to write
+the changed configuration file to another destination. Before actually
+writing, ConfigUpdater will automatically check that the updated
+configuration file is still valid by parsing it with the help of ConfigParser.
+
+Many of ConfigParser\'s methods still exists and it\'s best to look them
+up in the [module reference]. Let\'s look at some examples.
+
+## Adding and removing options
+
+Let\'s say we have the following configuration in a string:
+
+```python
+cfg = """
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+"""
+```
+
+We can add an *license* option, i.e. a key/value pair, in the same way
+we would do with ConfigParser:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+updater["metadata"]["license"] = "MIT"
+```
+
+A simple `print(updater)` will give show you that the new option was
+appended to the end:
+
+```ini
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+license = MIT
+```
+
+Since the license is really important to us let\'s say we want to add it
+before the `summary` and even add a short comment before it:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]["summary"]
+    .add_before.comment("Ada would have loved MIT")
+    .option("license", "MIT")
+)
+```
+
+which would result in:
+
+```ini
+[metadata]
+author = Ada Lovelace
+# Ada would have loved MIT
+license = MIT
+summary = The Analytical Engine
+```
+
+Using `add_after` would give the same result and looks like:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]["author"]
+    .add_after.comment("Ada would have loved MIT")
+    .option("license", "MIT")
+)
+```
+
+Let\'s say we want to rename `summary` to the more common
+`description`:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+updater["metadata"]["summary"].key = "description"
+```
+
+If we wanted no summary at all, we could just do
+`del updater["metadata"]["summary"]`.
+
+## Adding and removing sections
+
+Adding and remove sections just works like adding and removing options
+but on a higher level. Sticking to our *Ada Lovelace* example, let\'s
+say we want to add a section `options` just before `metadata` with a
+comment and two new lines to separate it from `metadata`:
+
+```python
+updater = ConfigUpdater()
+updater.read_string(cfg)
+(
+    updater["metadata"]
+    .add_before.comment("Some specific project options")
+    .section("options")
+    .space(2)
+)
+```
+
+As expected, this results in:
+
+```ini
+# Some specific project options
+[options]
+
+
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+```
+
+We could now fill the new section with options like we learnt before. If
+we wanted to rename an existing section we could do this with the help
+of the `name` attribute:
+
+```python
+updater["metadata"].name = "MetaData"
+```
+
+Sometimes it might be useful to inject a new section not in a
+programmatic way but more declarative. Let\'s assume we have thus
+defined our new section in a multi-line string:
+
+```python
+sphinx_sect_str = """
+[build_sphinx]
+source_dir = docs
+build_dir = docs/_build
+"""
+```
+
+With the help of two ConfigUpdater objects we can easily inject this
+section into our example:
+
+```python
+sphinx = ConfigUpdater()
+sphinx.read_string(sphinx_sect_str)
+sphinx_sect = sphinx["build_sphinx"]
+
+updater = ConfigUpdater()
+updater.read_string(cfg)
+
+(updater["metadata"].add_after.space().section(sphinx_sect.detach()))
+```
+
+The `detach` method will remove the `build_sphinx` section from the
+first object and add it to the second object. This results in:
+
+```ini
+[metadata]
+author = Ada Lovelace
+summary = The Analytical Engine
+
+[build_sphinx]
+source_dir = docs
+build_dir = docs/_build
+```
+
+Alternatively, if you want to preserve `build_sphinx` in both
+`ConfigUpdater` objects (i.e., prevent it from being removed from the
+first while still adding a copy to the second), you call also rely on
+stdlib\'s `copy.deepcopy` function instead of `detach`:
+
+```python
+from copy import deepcopy
+
+sphinx = ConfigUpdater()
+sphinx.read_string(sphinx_sect_str)
+sphinx_sect = sphinx["build_sphinx"]
+
+updater = ConfigUpdater()
+updater.read_string(cfg)
+
+(updater["metadata"].add_after.space().section(deepcopy(sphinx_sect)))
+```
+
+This technique can be used for all objects inside ConfigUpdater:
+sections, options, comments and blank spaces.
+
+Shallow copies are discouraged in the context of ConfigUpdater because
+each configuration block keeps a reference to its container to allow
+easy document editing. When doing editions (such as adding or changing
+options and comments) based on a shallow copy, the results can be
+unreliable and unexpected.
+
+For more examples on how the API of ConfigUpdater works it\'s best to
+take a look into the [unit tests] and read the references.
+
+# Notes
+
+ConfigUpdater started out as a helper for [PyScaffold], which still uses
+it to update the `setup.cfg` of existing projects. Since then it has
+become a useful tool in its own right for everyone who needs to change
+configuration files programmatically without losing the comments and
+formatting that humans put into them.
+
+[ConfigUpdater]: https://configupdater.readthedocs.io/
+[ConfigParser]: https://docs.python.org/3/library/configparser.html
+[PyScaffold]: https://pyscaffold.org/
+[uv]: https://docs.astral.sh/uv/
+[module reference]: https://configupdater.readthedocs.io/en/latest/api.html#configupdater.configupdater.ConfigUpdater
+[unit tests]: https://github.com/pyscaffold/configupdater/blob/main/tests/test_configupdater.py
+
+[Tests-image]: https://github.com/pyscaffold/configupdater/actions/workflows/ci.yml/badge.svg
+[Tests-link]: https://github.com/pyscaffold/configupdater/actions/workflows/ci.yml
+[Coverage-image]: https://img.shields.io/coveralls/github/pyscaffold/configupdater/main.svg
+[Coverage-link]: https://coveralls.io/r/pyscaffold/configupdater
+[Publish-image]: https://github.com/pyscaffold/configupdater/actions/workflows/publish-package.yml/badge.svg
+[Publish-link]: https://github.com/pyscaffold/configupdater/actions/workflows/publish-package.yml
+[PyPI_ver-image]:https://img.shields.io/pypi/v/configupdater.svg?logo=pypi&label=PyPI&logoColor=gold
+[PyPI_ver-link]: https://pypi.org/project/configupdater/
+[Conda-image]: https://img.shields.io/conda/vn/conda-forge/configupdater.svg?logo=Anaconda&label=Conda-Forge&logoColor=44A833
+[Conda-link]: https://anaconda.org/conda-forge/configupdater/
+[PyPI_down-image]: https://img.shields.io/pypi/dm/configupdater.svg?color=blue&label=Downloads&logo=pypi&logoColor=gold
+[PyPI_down-link]: https://clickpy.clickhouse.com/dashboard/configupdater
+[PyPI_py-image]: https://img.shields.io/pypi/pyversions/configupdater.svg?logo=python&label=Python&logoColor=gold
+[PyPI_py-link]: https://pypi.org/project/configupdater/
+[uv-image]: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json
+[uv-link]: https://github.com/astral-sh/uv
+[ruff-image]: https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json
+[ruff-link]: https://github.com/charliermarsh/ruff
+[mypy-image]: https://img.shields.io/badge/Types-mypy-blue.svg
+[mypy-link]: https://mypy-lang.org/
+[pytest-image]: https://img.shields.io/static/v1?label=‎&message=Pytest&logo=Pytest&color=0A9EDC&logoColor=white
+[pytest-link]:  https://docs.pytest.org/
+[rtd-image]: https://readthedocs.org/projects/configupdater/badge/?version=latest
+[rtd-link]: https://configupdater.readthedocs.io/
+[precommit-image]: https://img.shields.io/static/v1?label=‎&message=pre-commit&logo=pre-commit&color=76877c
+[precommit-link]: https://pre-commit.com/
+[MIT-image]: https://img.shields.io/badge/License-MIT-9400d3.svg
+[MIT-link]: LICENSE.txt
+[sponsor-image]: https://img.shields.io/static/v1?label=Sponsor&message=%E2%9D%A4&logo=GitHub&color=ff69b4
+[sponsor-link]: https://github.com/sponsors/FlorianWilhelm