You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 of gyp-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 add 3.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:
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: