[FFe] Remove Python 3.3 from Trusty

Bug #1295153 reported by Barry Warsaw
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
python3-defaults (Ubuntu)
Fix Released
Undecided
Unassigned
python3.3 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Several times this cycle we have discussed whether to drop Python 3.3 from Trusty, since upstream Python 3.4 final has been released, and has been available in Trusty for a while, and has been the default Python 3 version for a while. I've worked to fix known ftbfs and other issues with packages that worked in Python 3.3 but failed in 3.4 - a notable example is genshi, which upstream has committed fixes to their vcs and I've backported to the Debian and Ubuntu packages while we wait for a new upstream release.

There are no known 3.4 specific build failures in main: http://qa.ubuntuwire.com/ftbfs/
There are no python3.4 tagged bugs currently open: http://tinyurl.com/m8zqvjg

It makes sense to me that we should not carry Python 3.3 into an LTS. Just before the 3.4 final was released upstream, Python 3.3.5 was released, and it has been retroactively declared the last bug fix release of the 3.3 series. Python 3.3 now goes into security-only fix mode:

https://mail.python.org/pipermail/python-dev/2014-March/133213.html

Removing Python 3.3 will save archive space and reduce space in packages with extension modules (we need to identify them and rebuild them, and I'll coordinate with Doko on that).

Matthias Klose (doko)
affects: ubuntu → python3.3 (Ubuntu)
Revision history for this message
Matthias Klose (doko) wrote :

will work on this for the release ...

Changed in python3.3 (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-14.04-beta-2
status: New → In Progress
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

Considering the maintenance burden there would be maintaining two Python3 versions during the 5 year 14.04 support lifetime, I think this is a great idea. Even if there are a few Python 3.4 related rough-edges in some packages that might need SRUs early in 14.04's life, it still seems to me like removing Python 3.3 means a lot less work for you folks overall.

That's just my two cents as someone who uses Python3 heavily in production :)

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

We will also need a python3-defaults upload for that, dropping it as supported version.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in python3-defaults (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package python3-defaults - 3.4.0-0ubuntu2

---------------
python3-defaults (3.4.0-0ubuntu2) trusty; urgency=medium

  * debpython/version.py: Remove 3.3 as supported version.
 -- Matthias Klose <email address hidden> Sun, 23 Mar 2014 09:14:21 +0100

Changed in python3-defaults (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

python3.3 now removed, so python3-defaults should be able to migrate

Changed in python3.3 (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.