* fix logic in get_installed_runtime() to not error when a
new runtime gets installed (LP: #354228).

the root of the problem is that the debian_defaults file is not yet
the jaunty version when python2.6-minimal gets installed and pycentral
errors on versions it has no explicit knowledge about (from
debian_defaults)

Python3 installed under jaunty for me just now without a hitch. So at least if the upgrade from Intrepid to Jaunty has been completed then Python3 is available / installable thereafter under jaunty.

As I recall, my upgrade from intrepid to jaunty also entailed problems with the installation of python 2.6 being in conflict with the then standard use of python 2.5. That problem got corrected in the course of jaunty being upgraded daily (my common practice).

Please provide a clear "do this and then this" sequence to fix a trashed Intrepid->Jaunty upgrade. For example, while there's mention of an out of date python central control file causing this problem it would be nice if someone could write:
* in file /etc/blat/blat.conf
* add/common/delete the following lines
* run apt-get install python-central
or whatever. Please remember that what is second nature for you, the python maintainers, is black magic for many of us who just assume python runs.

Because the upgrade is currently so broken I'm assuming sequences of update/dist-upgrade can't untangle, and, so far this morning, that's been the case. If this should work, but just not for X hours/days/? until changes percolate through the mirrors I'd appreciate a simple "please hold tight till Saturday morning (or whatever) and then let a standard aptitude update && aptitude dist-upgrade fix it." --- Thanks.

I manually ran the dpkg -i command suggested above.
Then removed some wx python packages that were hanging.
After that, started getting some clean installs.
I'm running "apt-get upgrade" now and will polish off later.

I'm not sure, but is any action required for python3.0 to work?
Personally, I've installed it without any problems now that correct python-central is in the archive. It shows the "INFO: using unkown version ..." line. :)

though all of that was in the past 12 hours, so I'm guessing this is the
cause.

--
package python2.6-minimal 2.6.1-1ubuntu8 failed to install/upgrade:https://bugs.launchpad.net/bugs/354228
You received this bug notification because you are a direct subscriber of a
duplicate bug.

Status in "python-central" source package in Ubuntu: Fix Released Status in
"python2.6" source package in Ubuntu: Fix Released Status in "python3.0"
source package in Ubuntu: New Status in python-central in Ubuntu Intrepid:
Won't Fix Status in python2.6 in Ubuntu Intrepid: Won't Fix Status in
python3.0 in Ubuntu Intrepid: Invalid Status in python-central in Ubuntu
Jaunty: Fix Released Status in python2.6 in Ubuntu Jaunty: Fix Released
Status in python3.0 in Ubuntu Jaunty: New

I looked at /usr/bin/pycentral and it effectively uses py_compilefiles for all python versions instead of py3_compilefiles for python 3. But after altering pycentral accordingly, the python3.0-minimal-postinst tries to compile all python modules in python 3, and there are NOT compatible with python 3 yet.

The problem seems more general: this package's philosophy is 'just another version of python' while python3 is not backward compatible...