http://bugs.maemo.com/index.php?action=history&feed=atom&title=Python%2FHarmattan%2FPython_2.6_porting_tips 2026-04-06T10:33:57Z Revision history for this page on the wiki MediaWiki 1.15.5-7 http://bugs.maemo.com/index.php?title=Python/Harmattan/Python_2.6_porting_tips&diff=45838&oldid=prev 2011-11-24T17:51:55Z

<p><a href="/Python_2.6_porting_tips" class="mw-redirect" title="Python 2.6 porting tips">Python 2.6 porting tips</a> moved to <a href="/Python/Harmattan/Python_2.6_porting_tips" title="Python/Harmattan/Python 2.6 porting tips">Python/Harmattan/Python 2.6 porting tips</a></p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr valign='top'> <td colspan='2' style="background-color: white; color:black;">← Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 17:51, 24 November 2011</td> </tr> <!-- diff generator: internal 2026-04-06 10:33:57 --> </table>

wmoreira http://bugs.maemo.com/index.php?title=Python/Harmattan/Python_2.6_porting_tips&diff=45814&oldid=prev 2011-11-22T18:30:34Z

<p>New page: == Introduction == Porting a package to support Python 2.6 usually involves making it version agnostic, removing any explicit Python versioning. In Maemo versions prior to Maemo 5, the pa...</p> <p><b>New page</b></p><div>== Introduction ==<br /> <br /> Porting a package to support Python 2.6 usually involves making it version agnostic, removing any explicit Python versioning. In Maemo versions prior to Maemo 5, the packages had hardcoded support for Python 2.5, which can be demonstrated by all Python binding packages having &quot;python2.5-&quot; as prefix and consequently Python applications having these names also on their runtime dependencies. As Maemo 5 also used Python 2.5, these packages still worked without much problems, but as MeeGo 1.2 Harmattan uses Python 2.6 they will have to be ported.<br /> <br /> == Python 2.6 porting tips ==<br /> <br /> * First of all, consider using [[Documentation_for_pyside-assistant|pyside-assistant]] for taking care of the packaging of your application, instead of packaging it by hand. This way you can avoid dealing with various issues regarding Debian packaging and focus mostly in the application itself.<br /> * Any paths that, for some reason, have hardcoded &quot;python2.5&quot; or &quot;site-packages&quot; will have to be changed to &quot;python2.6&quot; and &quot;dist-packages&quot;, as these are the ones used on Python 2.6.<br /> * If your application uses any &lt;code&gt;python2.5&lt;/code&gt; prefixed 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, &lt;code&gt;python2.5&lt;/code&gt; can be changed to &lt;code&gt;python (&gt;= 2.5)&lt;/code&gt; without problems. If this is not possible or not desired, just change the dependencies to their &lt;code&gt;python2.6&lt;/code&gt; counterparts.<br /> * Also, this would be a good time for your package to be named following the new [http://www.debian.org/doc/packaging-manuals/python-policy Debian Python Policy] - the Policy states that Python packages must not have a fixed version number on its name (e.g. prefer python-foo instead of python2.6-foo).<br /> * One very particular case where changes are required is when some Python script uses identifiers that became reserved keywords in Python 2.6. As an example, old versions of python-xml had this issue, where the &lt;code&gt;as&lt;/code&gt; identifier (which became a reserved keyword in Python 2.6) was being used as variable name in some places. If these occurrences are not replaced, running the script will result in syntax errors.</div>

wmoreira