> 2.0 is available in debian-unstable, but for some reason isn't in > debian-testing. [...]
There is an "excuses" or "reasons" file or similar which you can check to find out. The most common causes are not building on one of the debian core platforms, or something which it depends on has an unsolved critical bug. Python fans who use debian should probably take a look and see if they can lend a hand to fixing it. Having Python 2.0 in Debian 3.0 would be a very good thing, but if no-one who knows the python build process helps out, it sounds like it might not happen. MJR
