[MeeGo-python] meego python 2.6 -> 2.7? (at least N900CE)

[Hugo Parente Lima]

On Thursday 14 July 2011 00:28:50 letters.random13 wrote:
> Hello,
> 
> i am interested in developing meego python apps using python 2.7 rather
> than the current meego python 2.6.  python 2.6 is basically a dead end; 
> python 2.7 seems preferable in every way and has been adopted on current
> major desktops (fedora, ubuntu) where lots of development occurs.

Sorry, but python 2.7 is also a dead end.

> i could not find any meego python roadmap regarding whether a version bump
> is planned or even possible.  (nor could i determine what version the new
> meego/harmattan uses, http://wiki.meego.com/Python/Harmattan)

Meego Harmattan uses Python 2.6.

> i expected some of this discussion / info to be in wiki or obs? perhaps
> there just isn't much community interest?
> http://wiki.meego.com/Python
> https://build.pub.meego.com/project/show?project=Project%3APython%3AModules
> https://build.pub.meego.com/project/show?project=Project%3APython
> but both obs are empty??  "This project does not have any packages yet."!
> ouch. maybe i am looking in the wrong place?
> 
> so, using the toolchain in the meego sdk on my desktop, i built python
> 2.7.1 manually following the instructions here:
> http://randomsplat.com/id5-cross-compiling-python-for-embedded-linux.html
> 
> (maybe i could have built it as a 'library' project directly in the sdk?)
> 
> a few modules weren't built;  they don't look problematic to me, but i
> didn't research further:
> ================
> Python build finished, but the necessary bits to build these modules were
> not found:
> _bsddb             _sqlite3           _ssl
> _tkinter           bsddb185           bz2
> dbm                dl                 gdbm
> imageop            readline           sunaudiodev
> 
> Failed to build these modules:
> _curses            _curses_panel      _elementtree
> pyexpat
> 
> =================
> 
> i didn't look into the mysterious 'random set of [additional] modules'
> already present in MeeGo core [http://wiki.meego.com/Python]
> (also, i'm running N900CE, so i don't know how it's random set of modules
> may differ from MeeGo core's set).
> 
> on the N900CE, the resulting build passes the basic(?) tests
> (test___all___.py) (for modules that were built):
> =================
> ...
> Following modules failed to be imported: ['ctypes.macholib.dyld',
> 'ctypes.macholib.dylib', 'ctypes.macholib.framework', 'ctypes.wintypes',
> 'dbhash', 'idlelib.AutoComplete', 'multiprocessing.sharedctypes']
> ok
> 
> ----------------------------------------------------------------------
> Ran 1 test in 18.907s
> 
> OK
> ====================
> 
> i am completely ignorant of meego packaging.  is python2.7 a 'package' that
> would intended to end up in one of the python obs?  or maybe it is excluded
> because there is a danger that it would conflict with MeeGo core python? 
> in this case the required workaround would be to reference it only as
> 'python2.7', never as 'python'.
> 
> as a user-installed app, i assume it should go in /opt for meego conformity
> (though /usr/local would be preferable).
> https://gabrbedd.wordpress.com/2011/03/24/meego-compliance-why-installing-t
> o-opt-is-a-good-thing/
> 
> then, the only issue is the standardized(?) hacks to add to (xterm?) env
> PATH (for /opt install; /usr/local/bin is already in PATH, at least in
> N900CE).  an 'idle' desktop app might be possible (_tkinter?...); some
> 'ipython in xterm' desktop app would be preferable, to me at least).
> 
> assuming any of this is useful to the meego python community, can someone
> point me in the right direction or to the proper (beginner!) documentation
> on some of these topics?
> 
> thanks

-- 
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.meego.com/pipermail/meego-python/attachments/20110714/1b728759/attachment.pgp>