[issue33180] Flag for unusable sys.executable

Steve Dower added the comment: Closing in favour of issue34725 -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue33180] Flag for unusable sys.executable

Change by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue33180] Flag for unusable sys.executable

Nick Coghlan added the comment: Also mentioning https://docs.python.org/3/library/multiprocessing.html#multiprocessing.set_executable, since it came up on the pickle-protocol-version-5 thread. -- ___ Python tracker

[issue33180] Flag for unusable sys.executable

Nick Coghlan added the comment: I'm not sure what the right solution is at the design level, but I did recently run into a quirk related to this in the embedding tests: on \*nix systems, PySys_SetProgramName affects sys.executable, while Windows ignores it. But certainly the intention is that

[issue33180] Flag for unusable sys.executable

Steve Dower added the comment: Looking at the docs https://docs.python.org/3/library/sys.html#sys.executable maybe we only need to clarify that it's not None only if it provides the normal command line? Then file bugs against all the libraries that don't work when it's not set? -- _

[issue33180] Flag for unusable sys.executable

New submission from Steve Dower : If you host Python in another program, it's likely that sys.executable is not pointing to a normal Python interpreter. This can cause libraries such as multiprocessing to fail when they try to launch the interpreter again. Worse, it may have launched your appl