🤖 New build scheduled with the buildbot fleet by @zooba for commit 49fa664 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

I triggered the buildbots mainly to test the new one we just added, this PR is still very open for updates :)

I see what you're trying to do here. In fact, I can't find a way to do it any better myself. That being said, I have a (minor) concern.

Your introduction of context.env_cmd while keeping context.env_exe around makes it unclear where each one should be used. Maybe better naming of the new context variable could help here. As it stands now, the reader has little chance to notice the subtle difference, so there's some danger of a future regression.

Your introduction of context.env_cmd while keeping context.env_exe around makes it unclear where each one should be used

Perhaps just documenting explicitly what they're for/why they're used would help, in particular if any other issues in this area come up relating to the MS-Store version of Python.

Perhaps just documenting explicitly what they're for/why they're used would help, in particular if any other issues in this area come up relating to the MS-Store version of Python.

I referenced the bug as an example of why we'd need this - unfortunately, this side of things keeps changing on the OS side too often, so I'm very hesitant to pretend in our source code that it's a known thing.

Also changed the member name to env_exec_cmd, which is what I had originally, but didn't like how long it was.

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

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

Hopefully there were no further concerns. We've got time to fix them up if so

GH-28811 is a backport of this pull request to the 3.9 branch.