Drop Python 3.8, 3.9 and 3.10 (end of life)
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
- Domain
- build-system, release
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.20251105cap kept for 3.9 wheels, which leavesconfluent-kafka[rules]on 3.14 without google-re2 wheels; typing_extensionsfallbacks marked "drop fallback once we require Python >= 3.11";uv lockfailing unless pyproject.toml is edited first (DEVELOPER.md);- bugs that only hit old versions, such as #2401 (
import confluent_kafka.aiofails 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
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from confluentinc/confluent-kafka-python
-
KIP-848 migration guide says never use assign()/unassign() with group.protocol='consumer'; it's only rejected after subscribePossibly taken @hidingmyname claimed this 22 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
confluentinc/confluent-kafka-python#2405 ·
Maintainers usually reply within 3 days
-
init_transactions docstring says the transaction.timeout.ms clock starts there; it starts at begin_transactionPossibly taken @hidingmyname claimed this 22 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 91/100
confluentinc/confluent-kafka-python#2404 ·
Maintainers usually reply within 3 days
-
Wrong type annotations for read only mapping types.Possibly taken @RasmusNygren claimed this 198 days ago. Openstatus:under-review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
confluentinc/confluent-kafka-python#2244 ·
Maintainers usually reply within 3 days
-
Wrong signature for `KafkaError`'s 1st parameter in `.pyi`Possibly taken @wgu9 claimed this 159 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
confluentinc/confluent-kafka-python#2243 ·
Maintainers usually reply within 3 days
-
Use joserfc instead of authlib.josePossibly taken @yvaishalirao claimed this 135 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
confluentinc/confluent-kafka-python#2242 · 2 comments ·
Maintainers usually reply within 3 days
All issues in confluentinc/confluent-kafka-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day