On 5/28/20, Adam Preble <adam.pre...@gmail.com> wrote: > > We had found what looked like a bug in the Python Launcher where it would > eat command line arguments meant for the script. I would find some stuff > missing from sys.argv in a script that just imports sys and prints out > sys.argv if I ran it directly in cmd.exe as "script.py." If I ran it as > "python script.py" then everything was good as usual.
Sometimes a user will open a script via "open with" and browse to python.exe or py.exe. This associates .py files with a new progid that doesn't pass the %* command-line arguments. The installed Python.File progid should be listed in the open-with list, and, if the launcher is installed, the icon should have the Python logo with a rocket on it. Select that, lock it in by selecting to always use it, and open the script. This will only be wrong if a user or misbehaving program modified the Python.File progid and broke its "open" action. -- https://mail.python.org/mailman/listinfo/python-list
