<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<br/>Since I'm not a developer, you can't completely rely on my thinking, but... It seems logical to optify Python (completely) in a way that makes application optificxation a necessity for Python developers. This would ensure an exception when people write apps and either (a) forget to optify (if it's left unautomated), or (b) force 'no' optification when building, therefore alerting devs to 'do it right.'
<br/>So, without being able to say which method would work best, I do think that optifying Python would benefit Maemo development beyond just the 'size' issue.
<br/>----- Original message -----
<br/>> On Wed, Oct 14, 2009 at 2:50 AM, Andrew Flegg <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:
<br/>> > Anderson wrote:
<br/>> > I plan to write up the conclusions and actions from the BOF as a follow-up to
<br/>> > Tim's notes, however on the Python issue would one of these two options work
<br/>> > well (from a point of view of expediency and pragmatism):
<br/>> > 1) Build Python with a prefix of /opt/maemo/usr.
<br/>> > Hardcode, either in an init script, or Python, PYTHONPATH to
<br/>> > /opt/maemo/usr/lib/python2.5:/usr/lib/python2.5:/...
<br/>> > 2) Add an init.d script which bind mounts /opt/maemo/usr/lib/python2.5
<br/>> > over /usr/lib/python2.5 at boot.
<br/>> I don't see any reasons why any of the above two would not work, so it
<br/>> might be interesting to at least try them with a small experiment to
<br/>> the python2.5-minimal package.
<br/>> But note that still no Python package (including applications) can
<br/>> have their executable scripts (i.e. those called directly by the
<br/>> interpreter) optified, otherwise a similar problem to optifying
<br/>> /usr/bin/python2.5 will occur.
<br/>> > Both of these would handle the issues with some Python modules not being
<br/>> > optified, and get Python out of the rootfs.
<br/>> We will give them a try, together with some more obvious size optimizations :)
<br/>> Anderson Lizardo
<br/>> OpenBossa Labs - INdT
<br/>> Manaus - Brazil