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

Robert report at bugs.python.org
Wed Nov 8 11:55:53 EST 2017


Robert <lma at posteo.de> 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 matches the documentation which is currently definitely not the case.

Of course one could add an extra passus to the docs like: "custom command names must not start with 'python'". But why include a special case (and make it less intuitive) without need?

By the way: We have a use case for this custom commands and I could image others had, too. Or how came that they were included?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31879>
_______________________________________


More information about the Python-bugs-list mailing list