Bump the python-requirements group in /requirements with 5 updates

[dependabot]

Bumps the python-requirements group in /requirements with 5 updates:

Package	From	To
sphinx-issues	3.0.1	4.0.0
sphinx-tabs	3.4.4	3.4.5
pyright	1.1.343	1.1.349
pytest	7.4.3	8.0.0
tox	4.11.4	4.12.1

Updates sphinx-issues from 3.0.1 to 4.0.0

Commits

• 50128ce Bump version and update changelog
• 0239bda Default to linking to GH sponsors URL for the :user: role (#131)
• 9d176de Dev Chores (#130)
• 08c376f Run pre-commit autoupdate
• See full diff in compare view

Updates sphinx-tabs from 3.4.4 to 3.4.5

Release notes

Sourced from sphinx-tabs's releases.

Version 3.4.5

What's Changed

• FIX: unpin docutils by @​agoose77 in executablebooks/sphinx-tabs#186

New Contributors

• @​agoose77 made their first contribution in executablebooks/sphinx-tabs#186

Full Changelog: executablebooks/sphinx-tabs@v3.4.4...v3.4.5

Changelog

Sourced from sphinx-tabs's changelog.

3.4.5 - 2024-01-21

Removed

• docutils version pin

3.4.2 - 2023-19-22

Added

• Testing for Python 3.11 and 3.12

Removed

• Dependency on unsupported sphinx_testing package

3.4.2 - 2023-19-22

Fixed

• tests for sphinx 7.2
• slice assignment in update_context(), which was removing JS scripts from other sphinx extensions/themes on pages where tabs were not used

Added

• Note in docs to clarify that include directive can't be used within a code-tab

3.4.1 - 2022-07-02

Added

• Weekly scheduled testing, to catch breaking changes in unpinned dependencies

Changed

• docutils version pin to allow use of verison 0.18.x

Removed

• sphinx version pinning - only the latest version of sphinx will now be fully supported, but previous versions will work if sphinx dependencies (i.e. jinja2) are managed correctly. This is inline with the approach at sphinx
• tests that were specific to older versions of sphinx and pygments
• jinja2 version pinning, as this is now pinned in latest version of sphinx

3.4.0 - 2022-06-26

Added

• Testing for sphinx 5
• Tesing for python 3.10

Fixed

• Fixed parsing of MyST content, where first line was being stripped

... (truncated)

Commits

• b8666a5 Fix numbering in CHANGELOG.md
• 8cceb66 Bump version number
• e6a00ac Update CHANGELOG.md
• 0632f4b FIX: unpin docutils (#186)
• See full diff in compare view

Updates pyright from 1.1.343 to 1.1.349

Commits

• 587e3f9 Pyright NPM Package update to 1.1.349 (#248)
• 9dc9813 [pyright updated to 1.1.348] Update Version (#247)
• daefe65 Pyright NPM Package update to 1.1.347 (#246)
• b16743c [pyright updated to 1.1.346] Update Version (#245)
• a13a839 [pyright updated to 1.1.345] Update Version (#244)
• 2186adf Pyright NPM Package update to 1.1.344 (#243)
• See full diff in compare view

Updates pytest from 7.4.3 to 8.0.0

Release notes

Sourced from pytest's releases.

pytest 8.0.0 (2024-01-27)

See 8.0.0rc1 and 8.0.0rc2 for the full changes since pytest 7.4!

Bug Fixes

• #11842: Properly escape the reason of a skip <pytest.mark.skip ref>{.interpreted-text role="ref"} mark when writing JUnit XML files.
• #11861: Avoid microsecond exceeds 1_000_000 when using log-date-format with %f specifier, which might cause the test suite to crash.

8.0.0rc2

pytest 8.0.0rc2 (2024-01-17)

Improvements

• #11233: Improvements to -r for xfailures and xpasses:
  • Report tracebacks for xfailures when -rx is set.
  • Report captured output for xpasses when -rX is set.
  • For xpasses, add - in summary between test name and reason, to match how xfail is displayed.
• #11825: The pytest_plugin_registered{.interpreted-text role="hook"} hook has a new plugin_name parameter containing the name by which plugin is registered.

Bug Fixes

• #11706: Fix reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.

• #11758: Fixed IndexError: string index out of range crash in if highlighted[-1] == "\n" and source[-1] != "\n". This bug was introduced in pytest 8.0.0rc1.

• #9765, #11816: Fixed a frustrating bug that afflicted some users with the only error being assert mod not in mods. The issue was caused by the fact that str(Path(mod)) and mod.__file__ don't necessarily produce the same string, and was being erroneously used interchangably in some places in the code.

  This fix also broke the internal API of PytestPluginManager.consider_conftest by introducing a new parameter -- we mention this in case it is being used by external code, even if marked as private.

pytest 8.0.0rc1 (2023-12-30)

See https://docs.pytest.org/en/latest/changelog.html#pytest-8-0-0rc1-2023-12-30 for the rendered changelog.

Breaking Changes

Old Deprecations Are Now Errors

• #7363: PytestRemovedIn8Warning deprecation warnings are now errors by default.

  Following our plan to remove deprecated features with as little disruption as possible, all warnings of type PytestRemovedIn8Warning now generate errors instead of warning messages by default.

  The affected features will be effectively removed in pytest 8.1, so please consult the deprecations{.interpreted-text role="ref"} section in the docs for directions on how to update existing code.

  In the pytest 8.0.X series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your pytest.ini file:

  [pytest]

... (truncated)

Commits

• 478f823 Prepare release version 8.0.0
• 6085900 [8.0.x] fix: avoid rounding microsecond to 1_000_000 (#11863)
• 3b41c65 [8.0.x] Escape skip reason in junitxml (#11845)
• 747072a [8.0.x] Update docstring of scripts/generate-gh-release-notes.py (#11768)
• 011a475 Properly attach packages to the GH release notes (#11839) (#11840)
• 97960bd Merge pull request #11835 from pytest-dev/release-8.0.0rc2
• 6be0a3c Prepare release version 8.0.0rc2
• 44ffe07 Merge pull request #11837 from pytest-dev/backport-11836-to-8.0.x
• 14ecb04 [8.0.x] testing: temporarily disable test due to hypothesis issue
• 41c8dab Merge pull request #11831 from bluetech/backport-11825-to-8.0.x
• Additional commits viewable in compare view

Updates tox from 4.11.4 to 4.12.1

Release notes

Sourced from tox's releases.

4.12.1

What's Changed

• Fix tox version requirement in docs by @​Viicos in tox-dev/tox#3184
• #3165 fixed Tox failing with --installpkg and multi testenvs by @​Stefanhg in tox-dev/tox#3186

New Contributors

• @​Viicos made their first contribution in tox-dev/tox#3184

Full Changelog: tox-dev/tox@4.12.0...4.12.1

4.12.0

What's Changed

• Exclude bots from generated release notes by @​hugovk in tox-dev/tox#3163
• Imply --parallel when --parallel-no-spinner is passed by @​tusharsadhwani in tox-dev/tox#3159
• Fix 'open an issue' link in development.rst by @​TheRealFalcon in tox-dev/tox#3179
• Fix the CI by @​gaborbernat in tox-dev/tox#3183
• Always pass FORCE_COLOR & NO_COLOR to the environment by @​hashar in tox-dev/tox#3172

New Contributors

• @​tusharsadhwani made their first contribution in tox-dev/tox#3159
• @​TheRealFalcon made their first contribution in tox-dev/tox#3179

Full Changelog: tox-dev/tox@4.11.4...4.12.0

Changelog

Sourced from tox's changelog.

v4.12.1 (2024-01-16)

Bugfixes - 4.12.1

- Fixed bug where running with --installpkg and multiple envs could not clean up between tests (:issue:`3165`)
v4.12.0 (2024-01-11)
Features - 4.12.0

• Always pass FORCE_COLOR and NO_COLOR to the environment (:issue:3171)

Bugfixes - 4.12.0

- ``--parallel-no-spinner`` flag now implies ``--parallel`` (:issue:`3158`)
Improved Documentation - 4.12.0

• -Fix open an issue link in development.rst (:issue:3179)

Commits

• 8eaf09f release 4.12.1
• 37b11d4 #3165 fixed Tox failing with --installpkg and multi testenvs (#3186)
• fa390ce [pre-commit.ci] pre-commit autoupdate (#3185)
• 3b403bc Fix tox version requirement in docs (#3184)
• 776718c release 4.12.0
• fc80080 Always pass FORCE_COLOR & NO_COLOR to the environment (#3172)
• 659f714 Fix the CI (#3183)
• 8406971 [pre-commit.ci] pre-commit autoupdate (#3182)
• 3f8f53d [pre-commit.ci] pre-commit autoupdate (#3177)
• 61547b0 Fix 'open an issue' link in development.rst (#3179)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.