PyMaemo/Python 2.6 porting guide
(→Introduction) |
(→Python 2.6 porting guidelines) |
||
| Line 19: | Line 19: | ||
=== Python 2.6 porting guidelines === | === Python 2.6 porting guidelines === | ||
| - | Porting a package to support Python 2.6 usually involves actually making it version agnostic. In Maemo versions prior to Fremantle, the packages had hardcoded support for Python 2.5, which can be demonstrated by all Python binding packages having "python2.5-" as prefix, and consequently | + | Porting a package to support Python 2.6 usually involves actually making it version agnostic. In Maemo versions prior to Fremantle, the packages had hardcoded support for Python 2.5, which can be demonstrated by all Python binding packages having "python2.5-" as prefix, and consequently Python applications also had these names on their Depends fields in debian/control. |
As long as Fremantle contains Python 2.5, though, packages that worked on Diablo should also work on Fremantle without changes. This happens because PyMaemo packages named python-<something> can also be installed by using python2.5-<something>. | As long as Fremantle contains Python 2.5, though, packages that worked on Diablo should also work on Fremantle without changes. This happens because PyMaemo packages named python-<something> can also be installed by using python2.5-<something>. | ||
| - | On the other hand, if we indeed upgrade to Python 2.6, this compatibility will not work anymore, and | + | On the other hand, if we indeed upgrade to Python 2.6, this compatibility will not work anymore, and packages will need modifications so they can work on Fremantle. |
| - | One possibility we are evaluating is to provide updates to PyMaemo packages in previous Maemo releases (e.g. chinook and diablo) so they can also be installed by using the version agnostic python-<something> name. This would allow most packages to be uploaded to all three releases (chinook, diablo and fremantle) without requiring specific changes only for Fremantle. | + | One possibility we are evaluating is to provide updates to PyMaemo packages in previous Maemo releases (e.g. chinook and diablo) so they can also be installed by using the version agnostic python-<something> name (along the old python2.5-<something> names). This would allow most packages to be uploaded to all three releases (chinook, diablo and fremantle) without requiring specific changes only for Fremantle. |
=== Porting tips === | === Porting tips === | ||
Revision as of 13:59, 19 June 2009
Contents |
Python 2.6 Porting Guide
Important: this document is still a draft. There are currently no planned dates for migration to 2.6, but it will be informed in advance on the maemo-developers and pymaemo-developers mailing lists, so that developers have some time to fix their packages.
This documents contains some general guidelines about how to port your Python application currently being used with Python 2.5 for working without problems with Python 2.6.
Introduction
Currently, Maemo 4.x (Diablo) has Python 2.5. Maemo 5 Beta (Fremantle) has this same version, but we are evaluating upgrading Fremantle to Python 2.6, so that developers can use the latest features, while keeping compatibility with Python 2.5. See the What’s New in Python 2.6 page for details.
This also means that we have no plans to migrate to Python 3.x during Fremantle life cycle. Using Python 2.6 is the best option because developers can use most 3.x features without breaking compatibility with Python 2.5. With Python 2.6, users can use a flag to check for possible incompatibilities with Python 3.x.
One question might arise: why not have both 2.6 and 3.x, or even 2.5, 2.6 and 3.x? We have thought about this, the problem is, with the current mechanism used in Debian and Ubuntu (which we also use), packages that install Python extensions need to be compiled for all supported versions, and all resulting binaries are installed in a single package. This means that some packages will simply double or triple their size even if only one version is installed and used.
Besides, if we have two or three versions available in the repository, there is a possibility that some packages would depend on e.g. 2.5 while others depend 3.x. So the user would need to have both versions installed in some cases.
For small devices such as the Internet Tablets, saving space is also a high priority, so we decided to support only a single version at a time during the life cycle of a Maemo distribution.
Python 2.6 porting guidelines
Porting a package to support Python 2.6 usually involves actually making it version agnostic. In Maemo versions prior to Fremantle, the packages had hardcoded support for Python 2.5, which can be demonstrated by all Python binding packages having "python2.5-" as prefix, and consequently Python applications also had these names on their Depends fields in debian/control.
As long as Fremantle contains Python 2.5, though, packages that worked on Diablo should also work on Fremantle without changes. This happens because PyMaemo packages named python-<something> can also be installed by using python2.5-<something>.
On the other hand, if we indeed upgrade to Python 2.6, this compatibility will not work anymore, and packages will need modifications so they can work on Fremantle.
One possibility we are evaluating is to provide updates to PyMaemo packages in previous Maemo releases (e.g. chinook and diablo) so they can also be installed by using the version agnostic python-<something> name (along the old python2.5-<something> names). This would allow most packages to be uploaded to all three releases (chinook, diablo and fremantle) without requiring specific changes only for Fremantle.
Porting tips
- Any paths that, for some reason, have hardcoded "python2.5" or "site-packages" will have to be changed to "python2.6" and "dist-packages", as these are the ones used on Python 2.6.
- If you use distutils for building your package, you must pass the --install-layout=deb flag for "setup.py install" command inside debian/rules in order to install the files to the proper locations. If you're using CDBS for this task, use the variable DEB_PYTHON_INSTALL_ARGS_ALL for passing the flag, e.g.:
- DEB_PYTHON_INSTALL_ARGS_ALL = --no-compile -O0 --install-layout=deb
- If your application uses any python2.5 package as one of its dependencies in any Depends field, you should drop the version number and add the version as a requirement - for example, python2.5 can be changed to python (>= 2.5) without problems. If this is not possible nor desired, just change the dependencies to python2.6.
- Also, this would be a good time for your package to use dependencies that follow the new Debian Python Policy, if that's the case - the Policy states that Python packages must not have a fixed version number on its name (e.g. prefer python-xml instead of python2.6-xml).