New submission from Robert <l...@posteo.de>: 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. "python" or "/usr/bin/python"). This means that if I want to provide a virtual command like "python-xyz" I get an error message "Invalid version specification: '-xyz'" instead of running the executable assigned to python-xyz. I would provide a Pullrequest if you accept this change in behaviour. ---------- components: Windows messages: 305072 nosy: mrh1997, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Launcher fails on custom command starting with "python" type: behavior versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31879> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
