RetroSearch Browse

Mon Mar 21 02:09:13 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109628.html

On 21/03/2011 11:15 AM, "Martin v. Löwis" wrote:
> Am 21.03.2011 00:43, schrieb Greg Ewing:
>> 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.
>
> I remain -1 on any proposal that uses subprocesses. It absolutely must
> be the launcher that is running Python. In fact, I'd call it
> "python.exe".

For clarity, could you please tell us which scenarios you have in mind 
that cause you to take that position, and why those scenarios couldn't 
ignore the existence of the launcher and stick with doing exactly what 
they do now (which presumably is to use python.exe directly)?

Thanks,

Mark

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109628.html below:

[Python-Dev] Draft PEP and reference implementation of a Python launcher for Windows