feat(python): update to python-build-standalone 3.13.2#26125
Conversation
0cbe235 to
274d1f6
Compare
Hmm, Excerpt: We are fetching the correct python build standalone according to I've seen this @jacksonrnewhouse - does anything here ring a bell (I'm still focused on the glibc portability work so if not, I'll just close this PR). |
a0a5f47 to
7506014
Compare
|
@jacksonrnewhouse - are you still looking at this? This is a breaking change (due to not having venv migrate functionality) and if it isn't going to land before beta we should probably close it (cc @dgnorton) |
d6b6225 to
00be390
Compare
e3d3c35 to
4b04222
Compare
jacksonrnewhouse
left a comment
There was a problem hiding this comment.
Okay, I think this is working now, lets get it into Beta.
Thanks @jacksonrnewhouse! Not for this PR but the timeouts in the tests make me wonder if this will be flaky. Perhaps it could be updated to poll for readiness in some manner? That said, merging as is. |
I forgot to mention that I tested this locally too (but with @jacksonrnewhouse's changes for python by default and fixes for the tests, we have tests everywhere during the builds, woohoo!!): |
Closes #26044
I need to do (essentially) a full round of testing for #26124, so figured I could use that testing to test this upgrade. As such, my plan is:
This change will cause all current venvs to stop working and require them to be recreated because we don't have a process for migrating existing venvs (see #26045 and #26062). That said, doing this now allows us to get this change in before beta and it will help avoid issues like #26062 for security updates (though it doesn't solve everything; still need what I outlined in the aforementioned issues).
If there are regressions with 3.13 in my testing, I'll revert.