[issue31879] Launcher fails on custom command starting with "python"

Eryk Sun added the comment: Whether it should be this way or not, here's how it currently works. The builtin virtual paths all end with "python": static SHEBANG builtin_virtual_paths [] = { { L"/usr/bin/env python", TRUE }, { L"/usr/bin/python", FALSE }, {

[issue31879] Launcher fails on custom command starting with "python"

Steve Dower added the comment: Not sure if Mark and Martin are part of an expert group, but neither are active in this area these days. For the original question, I have no idea why the command can't use a builtin name, so hard to say whether we'd change it. A summary of why it's broken and

[issue31879] Launcher fails on custom command starting with "python"

Change by Irit Katriel : -- nosy: +loewis, mhammond type: behavior -> enhancement ___ Python tracker ___ ___ Python-bugs-list

[issue31879] Launcher fails on custom command starting with "python"

Robert added the comment: Of course I do not know the initial ideas/philosophy of the launcher. But the current implementation supports these custom commands (for whatever reason). Thus I'd say they should work "properly". My view of "properly" is that the implementation

[issue31879] Launcher fails on custom command starting with "python"

Paul Moore added the comment: Personally I don't see the value (in general, I don't see much use for the whole custom command idea - making the launcher into a generalised shebang processor was never really a core feature). But I'm not going to say no if others find it

[issue31879] Launcher fails on custom command starting with "python"

Robert added the comment: I am still waiting for a OK (or denial) of my proposed Modification. I want to avoid that I start coding and when I am finished the PSF denies my PullRequest. Is anybody out there who can decide this or at least lead a discussion? --

[issue31879] Launcher fails on custom command starting with "python"

New submission from Robert : In the "py.ini" file it is possible to specifiy customized commands (see https://www.python.org/dev/peps/pep-0397/#customized-commands). Unfortunately it is not possible to specify custom commands beginning with one of the buildin names (i.e.