Conversation
Member
Author
|
Generated by Claude Code |
Contributor
|
Test collection failed on all matrix legs with "Failed: Marks cannot be applied to fixtures." in common.py's async_run helper (pytest.mark.asyncio(pytest_asyncio.fixture(func))). Not riscv64-specific: setup.cfg's [dev] extra pins pytest>=3.6 and pytest-asyncio!=0.11.0, both open-ended, so install_kivy_wheel dev resolves against today's PyPI and lands on pytest 9.1+. Verified by diffing the pytest 9.0.3 and 9.1.0 wheels directly: the same message lives in _pytest/deprecated.py (a PytestRemovedIn8Warning) through 9.0.3, and moves to _pytest/fixtures.py as a hard fail() in 9.1.0. A PIP_CONSTRAINT file caps pytest for the test install only, without touching setup.cfg's own bound or the shipped wheel's dependencies (kivy declares no pytest runtime dependency at all). Signed-off-by: Ludovic Henry <git@ludovic.dev>
<9.1 fixed the hard `Failed: Marks cannot be applied to fixtures.` error (that's pytest 9.1.0+ only), but the resolved 9.0.x still promotes the same underlying PytestRemovedIn9Warning to a collection ERROR at import time -- same test_app.py collection failure, different error class. pytest's own deprecation-escalation policy in the 9.0 pre-9.1 window apparently already enforces this one as fatal, not just warn-worthy. Drop the cap below the whole 8.x/9.0 cycle to pytest<8, the last major line predating this deprecation existing at all (my earlier diff of 7.4.4's _pytest/fixtures.py and deprecated.py found neither the warning nor the hard-error string). No change to pytest-asyncio's own version -- pip's resolver picks whichever release is compatible with pytest<8. Signed-off-by: Ludovic Henry <git@ludovic.dev>
luhenry
marked this pull request as ready for review
September 30, 2026 22:57
luhenry
added a commit
that referenced
this pull request
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kivy2.3.1Compiles kivy's Cython extensions against a from-source SDL2/SDL2_image/SDL2_mixer/SDL2_ttf stack. Upstream publishes no riscv64 wheel.
Mirrors upstream's
manylinux_wheels.yml.Differs from upstream
before-all- upstream's separate manylinux2014 docker run has no riscv64 imagepythonand zlib headers manylinux2014 hadCMAKE_POLICY_VERSION_MINIMUM=3.5- the image's CMake 4 rejects vendored deps' old minimumsMatrix: cp312, cp313 - 2.3.1 predates Python 3.14 (Cython capped at 3.0.11).
Testing
License: Wheel bundles SDL2, SDL2_image, SDL2_mixer, SDL2_ttf (zlib), libtiff, libwebp, libxmp, FreeType, HarfBuzz and libpng; upstream ships no licence text for them, so the build adds it.
Test counts pending CI.