Drop Python 3.8, 3.9 and 3.10 (end of life)

Open
#2,402 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start with pyproject.toml and DEVELOPER.md, then inspect the wheel build configuration and the typing_extensions fallbacks mentioned in the issue. Check how the proposed Python 3.11 minimum affects dependency constraints and release builds; done means the next release requires Python 3.11 and no longer builds or ships wheels for 3.8–3.10. A branch is already prepared, so coordinate with its author before taking this on.

Written by the indexing model from the issue text.

Description

Python 3.8, 3.9 and 3.10 are end of life (https://devguide.python.org/versions/), but confluent-kafka still declares requires-python >=3.8 and ships cp38-cp310 wheels. Keeping them costs:

  • a second cibuildwheel pass for cp315, because cibuildwheel 4 no longer builds 3.8 (#2400);
  • a google-re2<1.1.20251105 cap kept for 3.9 wheels, which leaves confluent-kafka[rules] on 3.14 without google-re2 wheels;
  • typing_extensions fallbacks marked "drop fallback once we require Python >= 3.11";
  • uv lock failing unless pyproject.toml is edited first (DEVELOPER.md);
  • bugs that only hit old versions, such as #2401 (import confluent_kafka.aio fails on 3.8).

Proposal: require Python 3.11 from the next release; pip on 3.8-3.10 keeps the last release that supports them. Earlier drops: 3.6 in 2.6.1 (#1592), 3.7 in 2.12.1 (#2105). I have a branch on top of #2400 ready.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GwUvhmzgfkiZ6vo4uGyesN

Dominant language
Python
Stars
528
Forks
977
Avg merge
2d 19h
Merged PRs (30d)
19

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from confluentinc/confluent-kafka-python

All issues in confluentinc/confluent-kafka-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.