Mark Hammond mhammond at skippinet.com.au
Mon Mar 21 00:52:48 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 21/03/2011 10:32 AM, "Martin v. Löwis" wrote:
>> The above raises an interesting question - if the launcher executed
>> Python in-process, what would sys.executable be?  I can imagine there
>> are few scenarios where it would be desirable to have it refer to the
>> launcher and a number of scenarios where it would be undesirable and
>> possibly break existing scripts.
>
> Interesting question. What is it in COM and ISAPI applications?

ISAPI isn't a good example - that uses DLLs.  For COM objects hosted in 
a .exe it will be pythonw.exe.  For Windows services it will be 
pythonservice.exe (which is part of pywin32 and is located simply by 
assuming it is next to win32service.pyd)

Regardless, I don't think they are very likely to break - my concern is 
more for "normal" scripts which construct a child process cmdline/argv 
using sys.executable...

Mark

---

• 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