-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing on pre-release (beta) versions of Python #219
Comments
We should wait for beta versions and then add them to GitHub Actions as we have done in the past. |
cclauss
changed the title
Testing on pre-release versions of Python
Testing on pre-release (beta) versions of Python
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, folks.
I had the idea to test on upcoming Python versions before they become stable.
Current results (Python 3.13): I'm happy to share that Python 3.13 Alpha 2 and
master
branch ofgyp-next
seem to be working okay together, at least at the time I'm writing this:Suggestion: If folks here want, I'm sure it wouldn't be too hard to modify the test matrix of the "Python tests" workflow to run against the prerelease Python version on a schedule, perhaps once weekly, or once monthly?
Let me know if this is something you are interested in, and I can look at the cleanest way to implement it into the workflow
.yaml
for CI. (Easiest thing would be to just add3.13
to the test matrix now, and test every PR/push against it, I suppose.)The text was updated successfully, but these errors were encountered: