-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.11 launcher fails with "Unable to create process" #95285
Comments
Maybe another release blocker? Edit: Possibly not - I rebuilt my Rust program, and cannot reproduce the issue there, now. So while there is definitely an issue, it's not as easily triggerable as I first thought. I updated my copy of rust, so maybe the rust stdlib changed how it calls |
I notice that there's a stray quote in that first example: ... \Python311\"py ... Was that a typo or actually present? |
Actually present. I'm assuming it comes from treating |
Yeah, something funky going on with the shebang command there it looks like. I'll take a look |
Okay, seems it's actually argv0 processing that's off, and you need to be launching from cmd.exe to trigger it (or probably through a custom subprocess command). |
(cherry picked from commit 7ac5bb3) Co-authored-by: Steve Dower <[email protected]>
(cherry picked from commit 7ac5bb3) Co-authored-by: Steve Dower <[email protected]>
Bug report
When running a
pip.pyz
file with thepy.exe
launcher (itself launched from a Rust program), the command fails with the error:Unfortunately, I haven't been able to isolate a fully reproducible test case so far. However, I have set
$env:PYLAUNCHER_DEBUG=1
and the output of the failing command isThe key issue seems to be
(note the unbalanced quotes) which appears to be a result of incorrectly parsing the following:
I can create the same debug output using the internal
_winapi.CreateProcess
function:So the problem appears to be when the command line passed to
CreateProcess
contains a double quoted but relative filename.Your environment
The text was updated successfully, but these errors were encountered: