Bruce Sass <[EMAIL PROTECTED]> writes:
> bms:~# ls -l /usr/bin/python*
> -rwxr-xr-x 2 root root 3040 Apr 10 02:09 /usr/bin/python
> -rwxr-xr-x 2 root root 3040 Apr 10 02:09 /usr/bin/python1.5
> -rwxr-xr-x 1 root root 3080 Jun 23 15:52 /usr/bin/python2
> lrwxrwxrwx 1 root root 7 Jun 24 18:34 /usr/bin/python2.0 ->
> python2
>
> ...'cause I've never seen a 3k python executable. So, using an
> explicit "python-wrapper" in the #! line is a step backwards to me.
$ ldd /usr/bin/python1.5
libpython1.5.so.0.0 => /usr/lib/libpython1.5.so.0.0 (0x4001f000)
...
$ ldd /usr/bin/python2.0
libpython2.0.so.0.0 => /usr/lib/libpython2.0.so.0.0 (0x4001f000)
...
These *are* real executables; it looks like all they do is call
Py_Main from whichever libpython they're linked against.
[...]
> I think it is perfectly reasonable for Debian to insist that a
> specific version of Python be installed, and that any Python programs
> distributed by Debian must work with a certain version of Python or
> better.
Agreed, although it seems OK to me to only expect them to work with
the current version, in any stable release of Debian. As the language
changes, adding keywords like "yield" and "div", etc., expecting full
forwards compatibility might be a little unreasonable.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
"Quiet, you'll miss the humorous conclusion."
