/usr/bin/env: python: No such file or directory

[Donn Cave]

Quoth Fernando Prez <fperez528 at yahoo.com>:
...
| If redhat is too lazy to upgrade their code in anaconda and other tools to 
| use python2, at least they could have the courtesy of putting explicitly 
| python1.5 calls in their OWN stuff, instead of forcing upon their users a 
| broken convention.
|
| I normally use mandrake (had been away from redhat for years) and only last 
| week was forced to deal with redhat again. What an ugly, messy excuse for a  
| linux distribution.

Does mandrake use Python for system software?

The last big go-round on this, the upshot as I recall it was that any
Python software had better be released with a dedicated interpreter.
More or less like what you propose.

It's too bad it has to be that way.  On one hand, it's unrealistic to
expect all developers to foresee this problem, and on the other it
seems pretty expensive for small to medium projects - maybe Redhat can
afford to tuck away 10Mb of their own python for their system software,
but even for them it's probably not exactly a selling point for Python.

I have never used Redhat Linux, but I would have to give them credit
for deploying Python software, and blame the Python community as much
as Redhat for the problem.  -- Why won't Redhat upgrade their software?
-- To what version?  Assuming it takes some time, and they start with the
official 2.x release, when they're finally shipping the upgraded software,
will 2.x even still be current, or at least capable of running recently
written Python software?  What a thankless task!

	Donn Cave, donn at u.washington.edu