Remove support for Python 3.10 by Pierre-Sassoulas · Pull Request #15163 · pytest-dev/pytest

Pierre-Sassoulas · 2026-10-11T11:01:32Z

Python 3.10 reached end of life in October 2026. Drop the exceptiongroup, tomli and asynctest dependencies and the version-conditional code paths that existed only for it.

RonnyPfannschmidt · 2026-10-11T11:20:53Z

🤖 Written by Claude Opus 5.5 via Claude Code for the pytest maintainers; I prompted it, it did the work, I read it.

The _find_lineno workaround in src/_pytest/doctest.py loses its coverage with this change. It now applies to 3.11 < 3.11.9 and 3.12 < 3.12.3. Until now, 3.10 was the only CI interpreter that went through it, and setup-python always installs the latest patch release.

We still support those interpreters (Debian 12 ships 3.11.2), so either:

add a floor job pinned to an old 3.11 patch release that only runs the affected tests (testing/test_doctest.py, set through _PYTEST_FILES the same way the twisted envs do it), or
mark the branch # pragma: no cover and accept that it's untested.

The changelog file also needs the PR number: changelog/15163.breaking.rst.

Generated by Claude Code

Pierre-Sassoulas · 2026-10-11T12:53:50Z

Thank you for the review @RonnyPfannschmidt , fixed in b10422d

bluetech · 2026-10-18T13:15:01Z

I'm preparing to release pytest 9.2 (I think I'll open an issue for it now). I think we might as well leave 3.10 support for this release and drop it in 10.0. (To be clear, our policy allows dropping old Python support in minor releases, just thinking since we've done the work for this release, might as well keep it). Let me know if you think differently.

bluetech · 2026-10-18T13:16:16Z

@@ -11,7 +11,7 @@


 if TYPE_CHECKING:


Probably we can drop the TYPE_CHECKING now.

bluetech · 2026-10-18T13:18:32Z

 [tool.black]
 # See https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#t-target-version
-target-version = [ "py310", "py311", "py312", "py313" ]
+target-version = [ "py311", "py312", "py313" ]


BTW, seems like this is missing py314. Or, given that the link says black supports deriving this info from project.requires-python, maybe can just drop it?

bluetech · 2026-10-18T13:20:07Z


 [tool.ruff]
-target-version = "py310"
+target-version = "py311"


BTW2, Ruff also says it considers project.requires-python for this https://docs.astral.sh/ruff/settings/#target-version, so should be possible to just drop this line as well.

bluetech · 2026-10-18T13:30:51Z

-        from datetime import timezone

-        tz = timezone.utc
+        tz = UTC


Personally I prefer datetime.UTC when datetime import is already available. A bit clearer.

Can't do it because there's a from datetime import datetime so it'd require a prior refactor.

bluetech · 2026-10-18T13:32:34Z

@@ -41,7 +41,7 @@


 if TYPE_CHECKING:


Can drop the TYPE_CHECKING

bluetech · 2026-10-18T13:32:39Z

@@ -16,7 +16,7 @@


 if TYPE_CHECKING:


Can drop the TYPE_CHECKING

bluetech · 2026-10-18T13:46:13Z

BTW, I remembered this Python 3.11 changelog

warnings.catch_warnings() now accepts arguments for warnings.simplefilter(), providing a more concise way to locally ignore warnings or convert them to errors. (Contributed by Zac Hatfield-Dodds in bpo-47074.)

I think we have a lot of cases in of the old pattern (with catch_warnings(): simplefilter()) in the docs and tests which we could now combine into one line. Thanks @Zac-HD :)

Python 3.10 reached end of life in October 2026. Drop the exceptiongroup, tomli and asynctest dependencies and the version-conditional code paths that existed only for it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

importlib.resources.abc exists since Python 3.11, so the version check was only needed for 3.10. Also refresh a docstring that still mentioned Python 3.10. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

With Python 3.10 gone, the latest patch releases that setup-python installs never hit the workaround for python/cpython#61648, which was fixed in 3.11.9 and 3.12.3. Add a `floor` tox factor that runs only testing/test_doctest.py, and a CI job using it on 3.11.2, the version Debian 12 ships. Also name the changelog fragment after the pull request. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Both are available in typing since Python 3.11, so the TYPE_CHECKING blocks that only existed for them are no longer needed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Both tools derive their target version from ``project.requires-python`` when it is not configured, so the explicit lists only had to be kept in sync by hand. Black is only run through blacken-docs, which does not read ``[tool.black]`` at all, so the section had no effect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Matches the local imports of the other datetime tests in the class. ``datetime.UTC`` cannot be used there because the local ``from datetime import datetime`` shadows the module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Since Python 3.11, ``warnings.catch_warnings()`` accepts the arguments of ``warnings.simplefilter()``, so the ``with catch_warnings():`` followed by ``simplefilter()`` pattern can be written in one line, in the docs as well as in the code and tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Pierre-Sassoulas · 2026-10-18T20:34:12Z

Did the warning refactor in 32422f4

Pierre-Sassoulas · 2026-10-18T20:38:48Z

The coverage fail comes from the catch_warnings(action="error") in testing/test_monkeypatch.py, in test_syspath_prepend_with_namespace_packages. That test is skipped in every CI job: it does pytest.importorskip("pkg_resources"), and pkg_resources isn't installed in any of our environments. Should we remove or should we make it run ?

Pierre-Sassoulas added type: refactoring internal improvements to the code dependencies pull requests that update a dependency file labels Oct 11, 2026

pyba-chronographer Bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Oct 11, 2026

Pierre-Sassoulas force-pushed the drop-python-3.10 branch from afb4878 to 196c757 Compare October 11, 2026 11:03

Pierre-Sassoulas force-pushed the drop-python-3.10 branch from 5558706 to b10422d Compare October 11, 2026 12:28

Pierre-Sassoulas marked this pull request as ready for review October 11, 2026 12:53

bluetech approved these changes Oct 18, 2026

View reviewed changes

Pierre-Sassoulas added this to the 10.0 milestone Oct 18, 2026

Pierre-Sassoulas and others added 7 commits October 18, 2026 22:31

Remove support for Python 3.10

2ce6365

Python 3.10 reached end of life in October 2026. Drop the exceptiongroup, tomli and asynctest dependencies and the version-conditional code paths that existed only for it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Drop the importlib.abc fallback in the assertion rewriter

c162530

importlib.resources.abc exists since Python 3.11, so the version check was only needed for 3.10. Also refresh a docstring that still mentioned Python 3.10. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Import Self and ParamSpec from typing at runtime

8374e00

Both are available in typing since Python 3.11, so the TYPE_CHECKING blocks that only existed for them are no longer needed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Import UTC locally in test_datetime_with_timezone

a6f995f

Matches the local imports of the other datetime tests in the class. ``datetime.UTC`` cannot be used there because the local ``from datetime import datetime`` shadows the module. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Pierre-Sassoulas force-pushed the drop-python-3.10 branch from 32422f4 to 21a7a51 Compare October 18, 2026 20:39

Merge branch 'main' into drop-python-3.10

6efc58c

Conversation

Pierre-Sassoulas commented Oct 11, 2026

Uh oh!

RonnyPfannschmidt commented Oct 11, 2026

Uh oh!

Pierre-Sassoulas commented Oct 11, 2026

Uh oh!

bluetech commented Oct 18, 2026

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

Pierre-Sassoulas Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech Oct 18, 2026

Choose a reason for hiding this comment

Uh oh!

bluetech commented Oct 18, 2026

Uh oh!

Pierre-Sassoulas commented Oct 18, 2026

Uh oh!

Pierre-Sassoulas commented Oct 18, 2026

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants