For me, if I want most existing python2 programs to work, I'd want to release my program as called "python", so "#!/usr/bin/env python" continued to work. If I

For me, if I want most existing python2 programs to work, I'd want to release my program as called "python", so "#!/usr/bin/env python" continued to work. If I'm not allowed to do that, then you are already adding a lot of friction to continuing to support existing python installs. Although, I wonder if you could claim you need to call it that for the programs to work?