Stub binary doesn't support `sys.executable` spawn/multiprocessing

[freakboy3742]

Describe the bug

The stub binary used to start an app is an effective replacement for the python.exe binary; however, it isn't a perfect replacements. multiprocessing in spawn mode will try to invoke sys.executable to spawn a child; it's also common to use subprocess or os.spawn to try and start sys.exectuable to run other Python code as a subprocess. However, the stub binary doesn't support this kind of execution.

Steps to reproduce

1. Generate a stub Windows app
2. Add a call to call multiprocessing.Process() and start it with .start()

The subprocess will call the parent process entry point, and fail.

Expected behavior

The function targeted by Process() should be invoked with the provided arguments.

Screenshots

No response

Environment

• Operating System: All Windows
• Python version: All
• Software versions:
  • Briefcase: 0.3.12

Logs

n/a

Additional context

See beeware/briefcase-macOS-app-template#7 for an analogous report on macOS.

One possible solution would be to add some logic to the stub binary to inspect to see if the parent process is "self"; if so, the execution of the app should be modified to behave as if it were a normal Python binary.

Any solution should also be ported to macOS (beeware/briefcase-macOS-Xcode-template#20) and Linux (beeware/briefcase-linux-flatpak-template#10)

[mhsmith]

This issue is worse on Windows, because "fork" mode is unavailable: see beeware/briefcase-macOS-app-template#7 (comment).

[Jzhenli]

what's the status for this issue?

[freakboy3742]

It's a currently open ticket. The issue is known to exist, and does not have a resolution.