Comment 4 for bug 654826

Hello Hantho and others

I just had the same 'exception(?)' when taking the command 'sudo apt-get upgrade'. I'd suppose this is no bug, due it lead not into an error while the upgrade process ran, but it's IMHO a lack, missing feature, whatever.

As Dag Odenhall posted in the opening entry, he added the content of '/usr/share/python/debian_defaults'. It seems, that someone can avoid the issue, by replacing the line with the stuff from here:

# all supported python versions
supported-versions = python2.5, python2.6, python3.0 (or whatever Version)

------------------
DON'T:
So if any of newbies read this post. Please don't set python3.0 as standard! When I tried this, it lead into a bunch of bad errors. It seems to me, that a lot of python programs, packages and installers still aren't made to run this version.

# the default python version
default-version = python3.0
-------------------

But one thing is, that I also don't understand what 'nothing to fix in maverick ' means. Why isn't e.g. my freshly installed python2.7 not in the list of the supported versions from debian_defaults? Unfortunately, I still don't understand the dependencies of the mentioned file. Where can I get more info?

Best regards to all,
Sebastian