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 test this out on. I'll give it a
try when I get a spare moment.
On Mon, May 14, 2001 at 12:00:14AM -0300, 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).
>
> Is there any possibility you were picking up a stray Python 1.5.2 binary in
> your path?
> --
> <a href="http://www.tuxedo.org/~esr/";>Eric S. Raymond</a>
--
Jamie Fifield
Software Designer [EMAIL PROTECTED]
AMIRIX Systems Inc. http://www.amirix.com/
Embedded Debian Project http://www.emdebian.org/
77 Chain Lake Drive 902-450-1700 x247 (Phone)
Halifax, N.S. B3S 1E1 902-450-1704 (FAX)
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
