Actually, this has been the reason to not choose 2.6 as the runtime at the time (3.0 was too "fresh" then ). The bug has been "fixed" since then, but see below why a upgrade during Maemo 5 is not feasible.

With the ratio of python applications already in extras considerably high (see http://mairas.net/pymaemo-stats/ for some numbers), it is very risky to switch from 2.5 to 2.6 or 3.0 in Fremantle, as they are binary incompatible (which affects bindings). This would break existing packages for no relevant gain, if not done carefully.

Supporting two runtime versions in Maemo is also not feasible, because you would need to have bindings compiled for both versions, which increases packages sizes considerably. It would be a problem also for Hildon applets, as just one Python loader can be loaded at a time (so in fact you would have either a 2.5 or a 2.6/3.0 loader, not both).

Of course none of these problems will exist once we begin working on Python support for the next Maemo release. It is not decided yet if it will be 2.6 or 3.0, but let's hold the discussion until that becomes relevant (i.e. when some public Harmattan SDK pre-release is made)

Note that code running on Python 2.5 will most probably work on 2.6 or 3.0 without changes, except for a few syntactic changes described on the Python documentation.

Regards,