I would guess that that is a good possibility. Now that you have mentioned
it, I'm not sure the Python 2 deb packages replace python 1, but rather put
everything in an alternate location. By installing Python 2.1, the 1.5.2
binaries were over written.
I think I have a system at home that I can
Jamie Fifield [EMAIL PROTECTED]:
I've noticed some incompatibilities with CML2 1.3.3 and the Debian packaged
Python 2.0 in woody. Is it safe to say that CML2 now requires Python 2.1?
(If so, please update the weeeb page).
Is there any possibility you were picking up a stray Python 1.5.2
I've noticed some incompatibilities with CML2 1.3.3 and the Debian packaged
Python 2.0 in woody. Is it safe to say that CML2 now requires Python 2.1?
(If so, please update the weeeb page).
I tried using it with the following Debian python packages:
python2-base (v 2.0-7)
python2-dev (v 2.0-7)
Jamie Fifield [EMAIL PROTECTED]:
I've noticed some incompatibilities with CML2 1.3.3 and the Debian packaged
Python 2.0 in woody. Is it safe to say that CML2 now requires Python 2.1?
(If so, please update the weeeb page).
I tried using it with the following Debian python packages:
On Friday 11 May 2001 15:15, Eric S. Raymond wrote:
Jamie Fifield [EMAIL PROTECTED]:
I've noticed some incompatibilities with CML2 1.3.3 and the Debian
packaged Python 2.0 in woody. Is it safe to say that CML2 now requires
Python 2.1? (If so, please update the weeeb page).
[Jamie's bug
