Bug#746709: transition: python3 -- change the default to 3.4
Control: tags -1 + confirmed
On 13/05/14 04:29, Scott Kitterman wrote:
> On Friday, May 02, 2014 20:07:00 Matthias Klose wrote:
>> Package: release.debian.org
>>
>> Jessie should ship with Python 3.4 as the default, and with 3.4 as the only
>> Python3 version. So lets start with making 3.4 the default. Two months
>> ago, the archive was buildable with 3.4 as the default (not directly
>> checked with unstable, but with the Ubuntu development release at this
>> time). The majority of the bugs seen with 3.4 [1] has been fixed in the
>> archive. A bug for python3.4 should be fixed for the release (#732703,
>> Barry Warsaw is working on this), and dh-python needs some updates.
>> Rebuilding extensions might affect ongoing transitions, but we don't have
>> yet that many for Python3.
>>
>> Matthias
>>
>> [1]
>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.4;users=debian-pyt
>> hon@lists.debian.org
>
> Looking at the Packages.qz for main/i386 I came up with this list of packages
> that need uploads/binNMUs once python3.4 is default (none of them support
> multiple python versions, so it can't be done in advance as the packages are
> now). It seems quite manageable to me.
>
> blender - binNMU after 3.4 default
> gdb - binNMU after 3.4 default
> geis - binNMU after 3.4 default
> yafaray - binNMU after 3.4 default
> libpeas - binNMU after 3.4 default
> libreoffice - binNMU after 3.4 default
> libsigrokdecode - binNMU after 3.4 default
> postgresql-9.3 - binNMU after 3.4 default
> pyqt5 - binNMU after 3.4 default
> znc - binNMU after 3.4 default
> morse-simulator - Needs source upload after 3.4 is default
>
> I think we can do this anytime after the current libreoffice and pyqt5 uploads
> migrate.
As discussed on IRC, let's do this one.
Reply to: