@pablogsal FYI, but I think I've got a fix for the current release, so we won't need to restart it.

@pablogsal FYI, but I think I've got a fix for the current release, so we won't need to restart it.

Nice! If you find the fix for the current release too complex, I can restart the release after work.

The quick fix was to run the build twice to make sure the file is there, so it just added a few minutes. Looks like it's past the point where it failed the first time though, so the only reason we might rebuild is if it's too obvious that the build scripts came from my fork instead of the main repo (but I don't think that'll be obvious).

Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖

Sorry @zooba, I had trouble checking out the 3.10 backport branch.
Please backport using cherry_picker on command line.
cherry_picker 6871fd0e8e5257f3ffebd1a1b2ca50e5f494e7f6 3.10

Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

Sorry, @zooba, I could not cleanly backport this to 3.10 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 6871fd0e8e5257f3ffebd1a1b2ca50e5f494e7f6 3.10

GH-27582 is a backport of this pull request to the 3.10 branch.