Hello, Many Python programs use constructs like #!/usr/bin/env python2.3 to load themselves. Many others use #!/usr/bin/python2.3. On most Debian systems, these are the same.
The submitter in #189473 claims that #!/usr/bin/env python2.3 is wrong because he has his own python2.3 on the path prior to the system's, and it doesn't necessarily have requisite libraries for the programs being run. Any opinions? -- John