Quoting John Goerzen [EMAIL PROTECTED]:
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
Quoting Jérôme Marant [EMAIL PROTECTED]:
Quoting John Goerzen [EMAIL PROTECTED]:
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
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
John Goerzen writes:
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
On Tue, 2003-08-12 at 06:50, John Goerzen wrote:
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
5 matches
Mail list logo