/usr/share/python/debian_defaults is missing an entry for python3.0

[LGB [Gábor Lénárt]]

I am not sure if it's a bug or not, it's reported as "INFO:" (so as "info" it's not bug, but I don't know then why it is useful to print this all the time) at installing/upgrading packages. Then quite often I see the following:

INFO: using unknown version '/usr/bin/python3.0' (debian_defaults not up-to-date?)

I've reported this against package python3.0-minimal since according to dpkg -S that package contains /usr/bin/python3.0. Version of python3.0-minimal package is 3.0.1-0ubuntu13. This is an up-to-date Ubuntu 9.04 system on x86 32 bit arch. I have no idea why python3.0-minimal is installed, I've just removed it with its dependencies (dpkg --purge python3-minimal python3.0 python3.0-minimal) and now everything seems to be normal. If that's info message is not a bug, but really just an info, please sorry for the noise here I've caused with this report. Thanks.

[Florian Diesch (diesch)]

Thanks for reporting this bug and any supporting documentation.

The file /usr/share/python/debian_defaults (from package python-minimal) is missing an entry for python3.0.

python-minimal:
  Installed: 2.6.2-0ubuntu1
  Candidate: 2.6.2-0ubuntu1
  Version table:
 *** 2.6.2-0ubuntu1 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[mknr22 (jhfamily123)]

another error launhpad crash

[Nomax (nomax)]

Also happens on x86_64 arch. Started after upgrade from Ubuntu 8.10 to 9.04.

[Philip Sterne (sterne-gmail)]

I also hit this problem. I did what I thought was the "obvious" solution by editing debian_defaults to include python3.0 as a supported-version.

This does take away all those irritating messages buts breaks the install process of some packages. Most notably those that use python-central (or pycentral).

[Florian Diesch (diesch)]

Philip Sterne <email address hidden> wrote:

> I also hit this problem. I did what I thought was the "obvious"
> solution by editing debian_defaults to include python3.0 as a supported-
> version.
>
> This does take away all those irritating messages buts breaks the
> install process of some packages. Most notably those that use python-
> central (or pycentral).

I included it as unsupported version which seems to work so far

   Florian
--
<http://www.florian-diesch.de/>

[Wouter van Heyst (larstiq)]

Ssince python3.0 breaks (some) backwards compatibility by design (http://www.python.org/dev/peps/pep-3000/) it is to be expected that packages written for 2.x will break on 3.

[Matthias Klose (doko)]

3.0 was removed in lucid

[Kojot350 (kojot350)]

Would you care to explain why this is removed by design?