Chris Gonnerman chris.gonnerman at newcenturycomputers.net
Wed Dec 26 08:53:47 EST 2001

• Previous message (by thread): /usr/bin/env: python: No such file or directory
• Next message (by thread): Offer to purchase Wexler.com
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

----- Original Message -----
From: "Trond Eivind Glomsrød" <teg at redhat.com>


> nbecker at fred.net writes:
>
> > The correct solution is for Redhat to put:
> > #!/usr/bin/python1.5
>
> The scripts don't depend on Python 1.5 - they depend on having
> certain modules available, with the same functionality as they
> were developed on.

True, but irrelevant.

If Red Hat did as nbecker at fred.net suggested, this would solve the
problem with incompatible Python installs, assuming only that the
system admin did not remove the 1.5 stuff before installing 2.x.

The fact that the statement

    #!/usr/bin/python1.5

at the top of the script does not SAY "certain modules" must be
available does not change the fact that it would work fine.

Another option would be to put

    #!/usr/bin/redhat-python

at the top of the script (creating the correct link in the process)
to make the purpose more transparent.

---

• Previous message (by thread): /usr/bin/env: python: No such file or directory
• Next message (by thread): Offer to purchase Wexler.com
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list