Skip to content

Conversation

neutrinoceros
Copy link

@neutrinoceros neutrinoceros commented Oct 17, 2025

Python 3.15 is still early in its development and I don't know that there's a precedent for adding "support" quite this early in the cycle, but given there are 0 failing tests at the moment, I figure it would might still be useful so:

  • later breaking changes are detected soon-ish
  • this would help any downstream package tested with tox knowing they can try out 3.15 pre-releases safely (or at least that issues might already be known here).

Anyway, I think this is worth a shot. Let me know if this is too early.

  • ran the linter to address style issues (tox -e fix)
  • wrote descriptive pull request text
  • ensured there are test(s) validating the fix
  • added news fragment in docs/changelog folder
  • [N/A] updated/extended the documentation

@gaborbernat
Copy link
Member

I'm always reluctant to add this so early because there's no easy way for the check to fail but not fail the entire CI 🤔 would want to have that before we commit to this.

@neutrinoceros
Copy link
Author

It could also run as a weekly cron job instead of regular CI. What do you think ?

@gaborbernat
Copy link
Member

That would work better 🤔

@neutrinoceros neutrinoceros force-pushed the tst/cp315 branch 2 times, most recently from 05d9474 to 93abb5c Compare October 17, 2025 16:00
@neutrinoceros neutrinoceros marked this pull request as ready for review October 17, 2025 16:00
@neutrinoceros neutrinoceros changed the title TST: add CPython 3.15 to test matrix TST: add weekly compatibility checks for CPython 3.15 Oct 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants