Skip to content
Discussion options

You must be logged in to vote

Hi there – thanks for raising this and for linking to the official devguide. You’re right: Python 3.10 is still in its “security-fix” phase until October 2026, so strictly speaking it isn’t EOL yet.

When I removed 3.10 in MR #384 I believed it was blocking a couple of dependency bumps; after double-checking, that assumption was incorrect.

I’m happy to restore 3.10 support until it actually reaches EOL (Oct 2026) or until a hard blocker appears.

Planned steps (can be done in one PR):

  1. Revert the classifiers & pyproject.toml change that dropped 3.10.
  2. Re-enable the 3.10 job in .github/workflows/ci.yml.
  3. Add a short note to CHANGELOG.md explaining that 3.10 support is back and will be maintain…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@janbjorge
Comment options

@AntonKarabaza
Comment options

Answer selected by janbjorge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants