Comment 2 for bug 1243065

I think the issue here is that while the fix for the upstream bug was committed [1] on the 19th Dec 2013, there hasn't been an upstream 2.7 point release that includes it, and thus that it can be packaged for Ubuntu.

If I'm not mistaken, the latest upstream point release (2.7.6) was on the 10th of November [2]. While it hasn't yet made it to Ubuntu (we've got 2.7.5, and 2.7.6 might not qualify for a Stable Release Upload), the main point is that the latest upstream release was made about one month before the fix was committed, thus there is no release from the 2.7.x series that includes it.

I think there is not an easy fix for Ubuntu 13.10 (backporting the fix might will most probably not qualify as SRU, and porting ubuntu-release-upgrader to Python 3.3, which might have the fix in Ubuntu 13.10 is probably not feasible for a stable release).

So in summary, this will probably be a "Won't fix" for Ubuntu 13.10. Not sure what to do with 14.04, as it might have exactly the same issue and we'll have the same constraints now that it has been released.

[1] http://hg.python.org/cpython/rev/3d805bee06e2
[2] https://www.python.org/download/releases/2.7.6
[3] https://launchpad.net/ubuntu/saucy/+source/python2.7/+changelog