On Tue, Oct 23, 2001 at 04:48:27PM -0500, Fabien Piuzzi wrote:
| Here is all the version:
|
| % dpkg -l|grep python
| ii python-base 1.5.2-18.4 An interactive object-oriented scripting lan
| ii python-gdk-iml 0.6.8-8 GTK gdk_imlib support module for Python.
| ii python-gnome 1.4.1-8 PyGNOME -- Python bindings for GNOME.
| ii python-gtk 0.6.8-8 GTK support module for Python.
| ii python-imaging 1.1.2-3 The Python Imaging Library.
| ii python-numeric 20.2.0-2 Numerical (matrix-oriented) Mathematics for
| ii python1.5-base 1.5.2-18.4 An interactive object-oriented scripting lan
| ii python1.5-dev 1.5.2-18.4 Header files and a static library for Python
| ii python2-base 2.0.1-1.1 An interactive object-oriented scripting lan
| ii python2.1-base 2.1.1-1.2 An interactive object-oriented scripting lan
|
| python -V is an unrecognized option
Huh. Upon further inspection, it seems that 1.5.2 doesn't have
this option but 2.x does.
| % head /usr/share/doc/python-gdk-imlib/examples/imlib/view.py
| #!/usr/bin/env python
I bet that 'python' in your path isn't the same version as the
python-gdk-imlib library was compiled with. There is much discussion
on debian-python now about how to manage multiple python versions and
how to resolve the broken dependencies that currently exist in many
python library packages.
Which python is found by 'which python'? If you run 'python' what
does it give as the version number?
As I look at the python-gdk-imlib package, it says "python-base (>=
1.5)" in its Depends: line. That is wrong and should really be ">=
1.5 , << 2.0" because it needs to be recompiled with python 2 and the
resultant .so put in the python 2 Lib directory.
If you change the first line to "#!/usr/bin/env python1.5" or run
"python1.5 view.py" it should work.
HTH,
-D
