Python
|
Size: 4316
Comment:
|
Size: 3643
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Here is everything you ever wanted to know about Python on Ubuntu <wink>. Well, probably not, but [[mailto:barry@ubuntu.com|let me know]] what essential information you think is missing and I'll work on updating it here. Or, since this is a wiki, you too can contribute! | Here is everything you ever wanted to know about Python on Ubuntu <wink>. |
| Line 16: | Line 16: |
| * Python 2.7 and Python 3.2 only in Ubuntu 12.04. With Precise Pangolin, we have dropped Python 2.6. | |
| Line 22: | Line 21: |
| == Plans for 12.10 == | == Plans for 16.04 == |
| Line 24: | Line 23: |
| It is a release goal to remove Python 2 from the desktop CD images for 12.10. There is a [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-python-versions|blueprint for UDS-Q]] on the subject, a [[https://wiki.ubuntu.com/Python/FoundationsQPythonVersions|wiki page]] describing the effort, and a [[https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AiT4gOXSkmapdFA1anRkWERsaXgtWnllUG9QWXhDVWc#gid=0|google spreadsheet]] tracking progress. | As of this writing, 15.04 (Vivid Vervet) was just released, and the Ubuntu Online Summit will be held in a couple of weeks. Now is the time to work on goals for 16.04 (X series). Previous work is captured in a historical [[https://wiki.ubuntu.com/Python/FoundationsQPythonVersions|wiki page]], and a [[https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AiT4gOXSkmapdFA1anRkWERsaXgtWnllUG9QWXhDVWc#gid=0|google spreadsheet]]. Both of these need to be updated. |
| Line 26: | Line 25: |
| == Longer term plans (e.g. 14.04) == | Overarching goals include: |
| Line 28: | Line 27: |
| * Move Python 2 to universe, port all Python applications in main to Python 3. We will never fully get rid of Python 2.7, but since there will also never be a Python 2.8, and Python 2.7 will be nearly 4 years old by the time of the 14.04 LTS release, it is time to relegate Python 2 to universe. | * Python 3 only on the default installs for desktop, server, touch, snappy images. (Some may already be there.) * Python 3.5 transition plan. * Removal of python-support. |
| Line 30: | Line 31: |
| * We will likely see [[http://www.python.org/dev/peps/pep-0398/|Python 3.3]] in time for 12.10. I recommend carrying both Python 3.2 and 3.3 for 12.10, with future support TBD. | == Longer term plans / stretch goals == |
| Line 32: | Line 33: |
| * Although it is too early to know right now (there won't even be a PEP until 3.3 is released), but we expect Python 3.4 to be the current release by the time of the 14.04 LTS. There's no way to tell what that transition might look like, so we just need to keep it in mind as we do our other Python work in Ubuntu and Debian. If I had to guess from previous LTS releases, we will likely carry just Python 3.4 for Ubuntu 14.04. | * How can we move Python 2 to universe given our intertwined build process and cross-pocket restrictions? * Can we better support PyPy and other alternative implementations (let's work with Debian on this) * What to do about ```/usr/bin/python``` (and influence [[https://www.python.org/dev/peps/pep-0394/|PEP 394]]) |
Python on Ubuntu
Here is everything you ever wanted to know about Python on Ubuntu <wink>.
The best thing to do is to start with the Python on Debian wiki page, since we inherit as much as possible from Debian, and we strongly encourage working with the great Debian Python teams to push our changes upstream. A useful way to look at it is this: because Ubuntu and Debian have different release cycles, namely that Ubuntu uses timed releases and Debian uses release-when-ready, we can use these to our advantage. Often, we can initiate big changes in Ubuntu first, using it to blaze a trail, and then systematically push those changes up into Debian, so that we can eventually remove as much of the delta from Ubuntu as possible. This was an effective model for both the Python 2.7 transition and the dh_python2 helper transition.
Here's a nice webified version of Barry's IRC tutorial on Python packaging. Thanks to Neil Wallace for putting this up.
Packaging best practices (including Python 3) for Python libraries in Debian
Deltas from Debian
The above wiki already describes where Debian deviates from upstream Python, and this section will outline how Ubuntu deviates from Debian. Hopefully, these deltas are even smaller.
- In Ubuntu python-minimal is an Essential package. In Debian it is not. This is a long term delta.
Bugs
Open bugs on Python packages in the archive: https://bugs.launchpad.net/~pythonistas/+packagebugs
Plans for 16.04
As of this writing, 15.04 (Vivid Vervet) was just released, and the Ubuntu Online Summit will be held in a couple of weeks. Now is the time to work on goals for 16.04 (X series). Previous work is captured in a historical wiki page, and a google spreadsheet. Both of these need to be updated.
Overarching goals include:
- Python 3 only on the default installs for desktop, server, touch, snappy images. (Some may already be there.)
- Python 3.5 transition plan.
- Removal of python-support.
Longer term plans / stretch goals
- How can we move Python 2 to universe given our intertwined build process and cross-pocket restrictions?
Can we better support PyPy and other alternative implementations (let's work with Debian on this)
What to do about /usr/bin/python (and influence PEP 394)
Python 3 porting
There are lots of resources on the 'net for porting to Python 3, but some may be difficult to find or follow. There are also lots of opinions on how to best port and support Python 3. Here in Ubuntu, we make and promote opinionated choices with the intent of making it easier for our users and developers. It's okay to disagree and discuss these choices, but we have had successful experiences with them and feel that they provide the technically best recommendations. To that effort, please refer to our guidelines for supporting Python 3 on Ubuntu.
All Ubuntu/Canonical driven development should be targeting Python 3 right now, and all new code should be Python 3-only. If you can't do this because of your dependency stack, let's talk.
Python (last edited 2017-01-25 23:23:00 by localhost)