[Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows
Nick Coghlan
ncoghlan at gmail.com
Sun Mar 20 00:23:21 CET 2011
More information about the Python-Dev mailing list
Sun Mar 20 00:23:21 CET 2011
- Previous message: [Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows
- Next message: [Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Mar 20, 2011 at 9:04 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote: > Am 19.03.2011 23:51, schrieb Nick Coghlan: >> On Sun, Mar 20, 2011 at 4:49 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote: >>> I, for example, will find issues with it if the implementation uses >>> CreateProcess at some point - the launcher should IMO run Python >>> directly, rather than creating a new process. This, in turn, will >>> probably mean that you cannot actually implement the PEP in Python. >> >> runpy performs basically that dance to implement >> _run_module_as_main(), so it's definitely possible. > > Does it also support loading a different interpreter version than the > one it is running? Ouch, no. I guess you're right, any Python based solution will need to create a child process. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows
- Next message: [Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list