updating to python2.6.7 in lucid and updating
Bug #788525 reported by
Matthias Klose
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python2.6 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: python2.6
(started discussion about this kind of update with Barry and Martin)
the python2.6 branch has a lot of bug fixes not present in the lucid python2.6 packages; it would be worth updating the python2.6 package to the 2.6.6 (or the 2.6.7) release. what would need to happen?
- review changes in the python2.6 branch, these should only be bug fixes (barry - done)
- backport the py_compileall / pycompile changes, needed for dh_python2 backport (doko)
- review locally applied bug fixes during the maverick and natty release cycle (doko)
the backport of dh_python2 is tracked in bug #788524
summary: |
- updating to python2.6.6 or .7 in lucid and updating + updating to python2.6.7 in lucid and updating |
Changed in python2.6 (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
2.6.6 was the last bug fix release for Python 2.6. 2.6.7 (planned for June 3, 2011) and beyond will be security-fix only releases. Yes, there are a *ton* of fixes in 2.6.6. See http:// hg.python. org/cpython/ file/2d760cb20e 1e/Misc/ NEWS
I'll review these to find any I think might affect Ubuntu, and check them against any distro patches we might have applied.