Summary

Pull Request Check List

• Added tests for changed code.
  • The CI fails with less than 100% coverage.
• New APIs are added to api.py.
• Updated documentation for changed code.

  • New functions/classes have to be added to docs/api.rst by hand.

  • Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.

    The next version is the second number in the current release + 1. The first number represents the current year. So if the current version on PyPI is 23.1.0, the next version is gonna be 23.2.0. If the next version is the first in the new year, it'll be 24.1.0.

• Documentation in .rst and .md files is written using semantic newlines.
• Changes (and possible deprecations) are documented in the changelog.
• Consider granting push permissions to the PR branch, so maintainers can fix minor issues themselves without pestering you.