Bump the python-packages group with 4 updates

[dependabot]

Bumps the python-packages group with 4 updates: parsl, pytest, botocore and jupytext.

Updates parsl from 2025.5.19 to 2025.5.26

Commits

• f2e5f5f Fix binding when user sets HTEx worker ports manually (#3838)
• b33555c Rearrange HTEX hold_worker because it holds managers, not workers (#3840)
• c23ae8d Remove interchange logging for sections where nothing happens (#3842)
• 94b5d61 Remove commented out code (#3843)
• bec91cf Improved error handling in the PBSProProvider (#3853)
• 6e2ebb9 Remove reassignment of interchange global logger (#3841)
• a2ce511 Update GH actions runner per GH image retirement (#3844)
• See full diff in compare view

Updates pytest from 8.3.5 to 8.4.0

Release notes

Sourced from pytest's releases.

8.4.0

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

• #11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

• #12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

• #12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

• #12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

  See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

• #10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

• #11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

• #12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

• #12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

• #12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

  This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.

• #12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.

  For example:

  # contents of src/domain.py
  class Testament: ...
  contents of tests/test_testament.py
  from domain import Testament
  def test_testament(): ...

  In this scenario with the default options, pytest will collect the class [Testament]{.title-ref} from [tests/test_testament.py]{.title-ref} because it starts with [Test]{.title-ref}, even though in this case it is a production class being imported in the test module namespace.

  This behavior can now be prevented by setting the new collect_imported_tests{.interpreted-text role="confval"} configuration option to false, which will make pytest collect classes/functions from test files only if they are defined in that file.

... (truncated)

Commits

• 315b3ae Prepare release version 8.4.0
• 1498ba3 Merge pull request #13467 from pytest-dev/towncrier-create
• e4389ac Remove resultlog from the docs (#13465)
• 64b2301 scripts/release: add missing build to towncrier call
• 4c205cf testing/plugins_integration: update Django (#13463)
• 4dcbcc9 Merge pull request #13458 from pytest-dev/dup-param-error
• 5293016 Merge pull request #13459 from pytest-dev/pyright-minor-fixes
• 7a48181 Add pyright configuration
• 9fc6db9 pytester: avoid confusing x self parameter
• 9aa198b mark/expression: fix self -> cls
• Additional commits viewable in compare view

Updates botocore from 1.38.23 to 1.38.28

Commits

• 39c9c08 Merge branch 'release-1.38.28'
• bec8e8d Bumping version to 1.38.28
• 2b03000 Update endpoints model
• 44d1891 Update to latest models
• 6b32855 Track retry mode and gzip feature ids (#3481)
• 994a156 Merge branch 'release-1.38.27'
• 7deb27e Merge branch 'release-1.38.27' into develop
• ff2e580 Bumping version to 1.38.27
• 9ac3725 Update endpoints model
• 261a369 Update to latest models
• Additional commits viewable in compare view

Updates jupytext from 1.17.1 to 1.17.2

Release notes

Sourced from jupytext's releases.

Version 1.17.2

Fixed

• The --set-formats argument takes precedence over pre-existing pairing information in the notebook (#1386)

Changed

• We have removed Python 3.8 from the list of supported Python version, and from the CI, as it has reached its EOL

Added

• ROOT-flavored C++ notebooks can be paired to .cpp files - thanks to Steven Gardiner for this contribution (#1384)

Changelog

Sourced from jupytext's changelog.

1.17.2 (2025-06-01)

Fixed

• The --set-formats argument takes precedence over pre-existing pairing information in the notebook (#1386)

Changed

• We have removed Python 3.8 from the list of supported Python version, and from the CI, as it has reached its EOL

Added

• ROOT-flavored C++ notebooks can be paired to .cpp files - thanks to Steven Gardiner for this contribution (#1384)

Commits

• 1289698 Version 1.17.2
• edd5b0b Add the text representation for the ROOT cpp example
• bbe80bb Add handling for ROOT-flavored C++ notebooks that use the ".C" extension
• 99f2b76 Reproduce and fix an issue with --set-formats (#1389)
• 7381980 Drop support for Python 3.8
• See full diff 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

[d33bs]

@dependabot squash and merge