| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Also needed in jit.yml and tail-call.yml: |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. It's a good idea to pin the Windows version and only upgrade it once it's well tested on newer Windows.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks! Pinning is a good idea in any case.
Question: does this new version have os.getpid?
Sorry, something went wrong.
Looks like they both do: |
Sorry, something went wrong.
|
Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10, 3.11, 3.12, 3.13, 3.14. |
Sorry, something went wrong.
(cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
Sorry, @hugovk, I could not cleanly backport this to 3.13 due to a conflict. cherry_picker 6e78a539bfb406238ec251ba01b7a1819e5c303e 3.13 |
Sorry, something went wrong.
|
Sorry, @hugovk, I could not cleanly backport this to 3.12 due to a conflict. cherry_picker 6e78a539bfb406238ec251ba01b7a1819e5c303e 3.12 |
Sorry, something went wrong.
|
GH-138752 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
Sorry, @hugovk, I could not cleanly backport this to 3.11 due to a conflict. cherry_picker 6e78a539bfb406238ec251ba01b7a1819e5c303e 3.11 |
Sorry, something went wrong.
|
Sorry, @hugovk, I could not cleanly backport this to 3.10 due to a conflict. cherry_picker 6e78a539bfb406238ec251ba01b7a1819e5c303e 3.10 |
Sorry, something went wrong.
|
Sorry, @hugovk, I could not cleanly backport this to 3.9 due to a conflict. cherry_picker 6e78a539bfb406238ec251ba01b7a1819e5c303e 3.9 |
Sorry, something went wrong.
|
GH-138753 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
GH-138754 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
GH-138755 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
…GH-138743) (cherry picked from commit 6e78a53) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
GH-138757 is a backport of this pull request to the 3.10 branch. |
Sorry, something went wrong.
|
GH-138758 is a backport of this pull request to the 3.9 branch. |
Sorry, something went wrong.
…138752) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
GitHub Actions is in the process of migrating windows-latest from windows-2022 to windows-2025:
actions/runner-images#12677
This is causing failures for forks which have already been migrated, for example:
https://github.com/picnixz/cpython/actions/runs/17610564159/job/50031376950#step:1:9
Upstream and my fork are still on 2022, but let's pin to windows-2022 so we can separately investigate and fix for 2025, and then pin to windows-2025.