Skip to content

16 repos skip 3.15 in the floors job #140

Open

Description

@lesnik512

All 16 repos have restored their ordinary CPython 3.15 dependency floors checks, including all five lite-bootstrap targets. The PRs below passed CI and merged.

Remaining Python 3.15t wheel blockers

These dependencies still lack compatible free-threaded CPython 3.15 wheels for Linux x86-64 as of 2026-11-21.

Dependency Affected floors jobs Upstream status
aiokafka faststream-concurrent-aiokafka and faststream-outbox through faststream[kafka] aio-libs/aiokafka#1198 and #1199 track Cython extension compatibility. The open PR addresses imports that re-enable the GIL. No dedicated 3.15t wheel publishing issue found.
watchfiles modern-di-fastmcp and lite-bootstrap's fastmcp target samuelcolvin/watchfiles#405 is open and directly adds abi3t wheels for Python 3.15 and newer.
grpcio lite-bootstrap's fastapi, faststream, and litestar targets through the OpenTelemetry gRPC exporter. modern-di-grpc also depends on it and is exempt from 3.15t. grpc/grpc#38762 tracks free-threaded Python support. #43172 is the draft build investigation. #41461 was a closed request for 3.14t wheels. No dedicated 3.15t wheel publishing issue found.
orjson lite-bootstrap's free target The upstream README describes free-threaded support as a possibility and says the project has no public issue or PR tracker.
pyroscope-io All five lite-bootstrap floors targets include it through their *-all extras. Tracked in modern-python/lite-bootstrap#171. grafana/pyroscope-python#176 merged and explicitly rejects free-threaded builds. The earlier 3.14t wheel CI proposal #166 is closed. No open 3.15t wheel issue found.

Re-run wheel-only resolution for the affected targets as upstream wheels become available.

Merged Python 3.15 checks

Original Python 3.15 blocker report

Every repo now tests CPython 3.15 in pytest, but 16 of them leave 3.15 out of the floors job. In each, the wheel-only install fails at the declared floors because some package has no 3.15 wheel there. CI6 allows dropping such an entry, so none of this is a violation. It is a gap: on 3.15 nothing checks that the declared floors install.

The 16 split into three groups by what unblocks them. The blocker listed is the first one the resolver hit; another may surface once it is cleared.

Fixable now with a 3.15 floor marker

These repos already declare floors per Python version (asyncpg>=0.31; python_version >= '3.14'). Narrowing the 3.14 line to == '3.14' and adding a >= '3.15' line at the first release with 3.15 wheels clears the blocker without raising the floor for older Pythons.

Repo Blocking floor First release with 3.15 wheels
db-retry asyncpg>=0.31 asyncpg 0.32.0
faststream-redis-timers pydantic>=2.12 (pins pydantic-core 2.41.1) pydantic 2.14.0
release-scope pydantic>=2.12 pydantic 2.14.0
httpware msgspec>=0.20, and pydantic>=2.12 behind it msgspec 0.22.0, pydantic 2.14.0 (which also needs typing-extensions>=4.16.0)
modern-di-aiohttp aiohttp>=3.13 aiohttp 3.14.4
modern-di-grpc grpcio>=1.82.1 (no markers yet) grpcio 1.84.0

grpcio 1.84.0 has no free-threaded wheel, which does not matter here: modern-di-grpc is exempt from the 3.15t entry.

Blocked upstream

No floor change here helps: PyYAML and aiokafka ship no 3.15 wheel in any release, and aiogram's pins keep out the pydantic release that does.

Package Repos How it gets in
PyYAML (newest is 6.0.3) compose2pod, semvertag direct dependency
jwks-client, modern-di-litestar through litestar
modern-di-fastmcp through fastmcp
that-depends through pre-commit in the dev group
aiokafka (newest is 0.14.0) faststream-concurrent-aiokafka direct dependency
faststream-outbox through faststream[kafka] in the dev group; its asyncpg>=0.31 and pydantic>=2.12 floors need the marker fix above as well
aiogram (newest is 3.31.0) modern-di-aiogram every release caps pydantic below 2.14, and no pydantic-core before 2.14's has 3.15 wheels; its aiohttp>=3.13 floor needs the marker fix above as well

Both

lite-bootstrap runs floors per framework target, and every target fails on 3.15:

  • free: orjson>=3.11.1; orjson 3.12.0 is the first with 3.15 wheels.
  • fastapi and faststream: the pydantic floors pin a pydantic-core with no 3.15 wheels; pydantic 2.14.0 is the first that works.
  • fastmcp and litestar: PyYAML, through those frameworks.

The marker fix clears the first three targets. The last two wait on PyYAML.

Activity

  1. lesnik512 commented on Nov 4, 2026

    @lesnik512
    MemberAuthor

    Checked 2026-11-04: still blocked, but the aiokafka blocker has changed.

    • aiokafka 0.15.0 now ships CPython 3.15 wheels. FastStream 0.7.8 and main still require aiokafka<0.15; wheel-only Linux 3.15 resolution fails for both faststream-concurrent-aiokafka and faststream-outbox (including its dev group). No dedicated upstream 0.15 support issue/PR found.
    • PyYAML remains 6.0.3 without 3.15 wheels; aiogram 3.31.0 still requires pydantic<2.14.

    Next trigger for the FastStream repos: a FastStream release allowing aiokafka 0.15. No free-threaded wheels ship in aiokafka 0.15.0.

  2. lesnik512 commented on Nov 4, 2026

    @lesnik512
    MemberAuthor

    Upstream aiokafka 0.15 support is now tracked in ag2ai/faststream#3326 (open).

    Local verification: 1,102 Kafka tests passed with aiokafka 0.15, including 345 connected tests against Redpanda 26.2.6. Python 3.10 still resolves aiokafka 0.14 and passes the in-memory suite.

    faststream-concurrent-aiokafka and faststream-outbox remain blocked until a FastStream release includes the relaxed cap. Then restore their ordinary 3.15 floors entries and run CI; 3.15t still lacks aiokafka wheels.

  3. lesnik512 commented on Nov 4, 2026

    @lesnik512
    MemberAuthor

    Upstream CI passed on ag2ai/faststream#3326, including 345 connected tests against Kafka 8.0 with aiokafka 0.15.0 and the Python 3.10 checks.

    Still waiting for the PR to merge and a FastStream release containing it. Then we can restore the ordinary Python 3.15 floors entries in faststream-concurrent-aiokafka and faststream-outbox and run CI.

  4. lesnik512 commented on Nov 13, 2026

    @lesnik512
    MemberAuthor

    Rechecked on 2026-11-13 using current PyPI metadata and wheel-only resolution for CPython 3.15 on x86_64 Linux. All remaining blocker groups still fail resolution, so no floors entries can be restored yet.

    • PyYAML 6.0.3 remains the latest release and has no CPython 3.15 wheels.
    • aiogram 3.31.0 still requires pydantic<2.14; the compatible pydantic-core versions have no CPython 3.15 wheels.
    • fix(deps): allow aiokafka 0.15 ag2ai/faststream#3326 has merged. FastStream 0.7.8 is still the latest published release and requires aiokafka<0.15, excluding the release with CPython 3.15 wheels. The next trigger is a published FastStream release containing that change. Free-threaded aiokafka wheels remain absent.

    Reproduction: run uv pip compile <requirements.in> --python-version 3.15 --python-platform x86_64-unknown-linux-gnu --only-binary :all: with each of PyYAML>=6.0.3, aiogram==3.31.0, and faststream[kafka]==0.7.8 as the input requirement. Each exits 1 with an unsatisfiable wheel-only resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions