Depending on system,
Executable Python scripts, starts with:
#!/usr/bin/env python #!/usr/bin/env python2 #!/usr/bin/env python3...
For python py3k it is provided in documentation I should/can use it with version number, so I do this:
But I've found a problem with py2k scripts.
While in py2k documentation it is written to use :
#! /usr/bin/env python ,
How to package (configure,make) and/or prepare python scripts for distribution to handle that ?
I ask about making software packages that can be run easily by users (without modyfing their environment)
Can I do the same trick for python py2k scripts as for python py3k scripts and set it as :
#!/usr/bin/env python2 ?
Can I be sure that each python py2k distribution contains
python2 file, so
#!/usr/bin/env python2 will work ?
If yes, why it is not proposed as standard, for example in python py2k documentation ?