On Mon, Dec 11, 2006 at 10:20:58PM +1030, Berndt Josef Wulf wrote:
> I'm sure it is Python.h. The problem I think is the way we install python for 
> multiple versions where the path becomes somthing like 
> <prefix>/include/<python-<PYVERSION> and the binary becomes 
> <prefix>/bin/python<PYVERSION>

Both is done e.g. by Debian as well. Nothing new. I'm not aware of any
major system which is not doing the same.

> I encounter this kind of problem with python scripts installed by third party 
> packages. Most scripts define
> 
> #!/usr/bin/env python

Kill the authors. This is just stupid for any bigger package as nothing
guaranties that Python is the search path (certainly a bad assumption
for pkgsrc scripts). Second it does not give any idea about whether the
python script found that way can actually support the script. This is a
concern for me as I often have to run multiple Python versions, some for
old scripts where the extensions are not portable, the newest version
where I care for speed etc.

Joerg