shebang backwards compatibility

[felixhirt]

The problem: backwards compatibility with old python scripts using non-standard shebang lines is not available. Old py launcher supported such shebangs, new one cannot.
example:
python script:

#!/opt/indel/bin/indel-python2
import traceback
import time

py.ini:

[commands]
/opt/indel/bin/indel-python2=C:\indel\share\python\python27\python.exe
/opt/indel/bin/indel-pythonw2=C:\indel\share\python\python27\pythonw.exe

Could you add a way to define non-standard shebangs again? e.g. in pymanager.json a list of shebangs and target exes like in old py.ini?

Alternative: We installed py launcher again, but this is legacy

[zooba]

I really don't want shebangs to become a "run arbitrary executable" feature here - a lot of malicious code loves to hide behind legitimate programs, and we want py.exe to be treated as a legitimate program. So that really puts me off having it launch anything that it isn't responsible for.¹

Would it work if you could map an arbitrary command like /opt/indel/bin/indel-python2 to a -V option, like "/opt/indel/bin/indel-python2": "-V:PythonCore\\2.7"? Non-standard Python installs can be registered using PEP 514 for this (you can test if it's already registered with py -V:2.7), and managed ones (which we hope will be the future) are of course included.

If you really do need a tool that handles shebangs to arbitrary executable, then I think you may need to find it elsewhere. We want the Python launcher to launch Python, not anything.

Footnotes

1. Malicious code can, of course, replace those legitimate executables and "win" that way, but that's outside of our threat model. ↩

[felixhirt]

Yes, this should work for us, would be great if you can implement this

[zooba]

There is now a beta release at https://www.python.org/downloads/release/pymanager-263b1/ with the change to add the configuration setting I proposed. The docs are currently at https://github.com/python/cpython/pull/150931/changes but should be on the website today/tomorrow.