Re: help with seemingly Debian-specific python bug

es the layout of PyObject, so non-debug C extensions access the fields of that wrong. [This of course makes a debug build pretty hard to use...] -- |>|\/|< /------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |[EMAIL PROTECTED]

Python 2.3 as default?

What's the word on making the default version of python to be 2.3 instead of 2.2, now that 2.3 is released? -- |>|\/|< /------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |[EMAIL PROTECTED]

Re: What should we do now?

s are essential base programs in Debian -- it would be stupid to fiddle with them, unless you know what you're doing] I see it as: this package I installed worked, and I don't care whether it's written in python or perl or tcl... Now, I've compiled my own python, and the package doe

Re: libwxgtk2.2-python (fwd)

fficult to fix when upgrading a package to depend on 2.1 instead of 2.0? (I can't) -- |>|\/|< /--\ |David M. Cooke |[EMAIL PROTECTED]

Re: python2.1 et al.

h like the 'gcc' package, whose only purpose is to set what is the default python interpreter for Debian? It would depend on python2.1-base. -- |>|\/|< /------\ |David M. Cooke |[EMAIL PROTECTED]

Re: Status report on python2 transition (possible solution)

ou could split the argument on spaces -- although I'm not sure if other Unices (the Hurd, anyone?) pass the rest of the line or just the first argument. Another alternative would be #!/usr/bin/deb_py_ver 1.5.2- and #!/usr/bin/deb_py_ver 1.5.2-2.1.1 That's one argument. -- |>|\

Re: Python 2.1 out

t depend on python-base that would have to be checked for compatibility with Python 2.1. I think it's safe to say that wholesale use of 'python -W ignore' would be unwarranted, because a lot of other stuff has to checked any way ;-) -- |>|\/|< /--\ |David M. Cooke |[EMAIL PROTECTED]