Mark Hammond wrote: > The above raises an interesting question - if the launcher executed > Python in-process, what would sys.executable be? I think it should be the actual Python executing at that moment, not the launcher. This is the least change from current behaviour and therefore least likely to break existing code. If some new code that's aware of the launcher wants to use it, a new attribute such as sys.launcher could be provided to make it easy to find. Or maybe a launch() function that runs a specified script using launcher semantics. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4