Yes, I maintain several packages which are* compatible with either Python 2 or 3. Those packages have a defined entrypoint which begins with `#!/usr/bin/python`

Yes, I maintain several packages which are* compatible with either Python 2 or 3. Those packages have a defined entrypoint which begins with `#!/usr/bin/python`. For packages which are Windows-compatible, they end in .py. If those two things don't cause the script to be executed by Python then frankly the user's system is broken and I'm not going to worry about it. (Depending on what you're writing, `#!/usr/bin/env python` may be a better option, so that you respect the PATH - including venv's.) * Well, they were compatible, but I no longer test against Py2.