Thursday, 20 March 2014

Remove Python 3.3 from Trusty

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTKwEtAAoJEBJutWOnSwa/YxMP/3o7p26E+IroASbxSlZDIWgq
NL1lx9fiGRiXzLea4xhrXfvjW/hYJKR+4gmKDvIfTAMvSGA5LKfuFjJeg8b/hidw
6pbwAe6gvdMu4weAuHMurvQEP3i1cvyoFyFmEsL0I/ohpK6XbpD0FxZjQrFtgxTF
R/CVKhtHOl/gyDgdrZbgIyKKvIazmHLodx7hAUpoNn8m4pHGNdYxA7vlQPvhktFB
251aqLMRDXYIwwP5OpWfz6HgWHzODeCPNY8kRUWdTkb2iEx7xN/xHAOOgWPa41XW
zCXbGWX7SlXUH8SNpmbx5Ltd7NTJ6FIaKERizPc86objcrA7XjSMbktbQtL8LwAS
rX9o0wDzCrBWJGYJD/ZKQZ7knR3ffEscxPRyWR4pHDYVF/SiLFFtnLC7kc6PQu/Q
V3xGDC+B2a+wFiPxY9RszcfKc094cGkp/iKUJI9IYiegeUhoUl93grCAW65pcknP
+JlxZOlK2viXfO7p66N4qPRtxNFpuwFBTNswnKmhoafEH+n9q6DzzgqUANeoAdgb
tQFEdRDBvH/mBsWBiD3G42NzW9i9E5ZlUaTTnbKQqU1LzMjS/k4yTmrbpJs+v+3E
4cBhpZOt4dmcR+/CYCyORO2Xt5inHYdQEuqCHQ3Mn+2gjLRDKQ9jsG3pCGZ5pgi+
hyPpTPZpCKvWnQKu5i5K
=eUYU
-----END PGP SIGNATURE-----
I just filed LP: #1295153 for removing Python 3.3 from Trusty.

https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1295153

Matthias and I have been in favor of this for a while, given that it looked
like Python 3.4's release schedule would nicely align with ours. In fact, it
all worked out, with Python 3.4 final having been released on March 16, 2014.

Python 3.3.5 was released on March 8, 2014 and was retroactively declared the
last bug fix release for Python 3.3. It now enters security-only mode for the
duration of its lifecycle.

Python 3.4 is a great release[1], and while we did find a few
incompatibilities[2] leading to package build failures, all have been
addressed now as far as we know.

I think it's better overall for us to drop Python 3.3 from Trusty and support
only Python 3.4 for the LTS. We will need to identify Python 3 extension
module packages and rebuild them to reduce their size.

Cheers,
-Barry

[1] http://docs.python.org/3.4/whatsnew/3.4.html

[2] Notable examples:

- The AST has changed and this lead to breakages of genshi. Upstream genshi
committed some fixes to their vcs which I've backported to Debian and
Ubuntu, while we wait for a new upstream release.

- The semantics of __file__ have changed; it is now guaranteed to be an
absolute path. While it's highly discouraged for packages to use __file__
(use the pkg_resource API instead), oneconf was relying on the relative
paths of previous releases. I've fixed that bug and uploaded a new version.