On Thu, Oct 08, 2009 at 15:30 +0200, Jan Wedel wrote: > > Do you have a pointer to documentation or a text that says so? > > Yes : > > http://codespeak.net/pypy/extradoc/eu-report/D11.1_PyPy_for_Embedded_Devices-2007-03-26.pdf > > > It should be possible with future versions of PyPy to use the > framework in other ways in the embedded context > > for instance by shipping a restricted version of the interpreter, > dedicated to the interpretation of a given > > set of programs. > > I think I read something more precise but I couldn't find it anymore.
That use case study mainly worked with using RPython and says that its efficiency is not far from using C. I guess this could be extended to also apply for Java-ME so that an RPython program would run as fast as native Java. A restricted version of the existing Python interpreter is quite a lot of work and it's unclear how successful it could be. Python might be an easy-to-read and to-learn language but it's internals are quite complex, unfortunately. best, holger > -----Ursprüngliche Nachricht----- > Von: holger krekel [mailto:[email protected]] > Gesendet: Donnerstag, 8. Oktober 2009 15:17 > An: Jan Wedel > Cc: [email protected] > Betreff: Re: [pypy-dev] Does PyPy supports Java ME? > > Hi Jan, > > On Tue, Oct 06, 2009 at 15:15 +0200, Jan Wedel wrote: > > I was currently working on a port of PyMite (8-Bit MCU port of > CPython) > > to Java ME. I already got the interpreter working so that basic Python > > > scripts could run as code images on a mobile java IMP device. Actually > > > we need Python interpreters on different embedded platforms supporting > > > either C or Java ME (IMP). I discovered a lot of problems including > the > > missing class implementation of PyMite. > > > > Then, by recommendation, I found PyPy. It looks as if it is exactly > what > > I was looking for and I read that it is specifically designed to > support > > embedded platforms. > > Do you have a pointer to documentation or a text that says so? I > wouldn't > see PyPy this way. However, we do have a pypy-c version that works on > Maemo and is more efficient for larger amounts of user objects. We also > have ideas how to reduce RSS size after interpreter startup, > mostly tied to pypy-c so far, though. > > In principle it's also possible to translate RPython to C or JVM > and avoid interpretation alltogether. RPython is >50 times faster > than CPython but less convenient to work with than regular Python > so only makes sense to consider for special purposes. And is > probably best learned in collaboration with developers who know > how to work with it and are willing or paid to help. > > cheers, > holger > > -- > Metaprogramming, Python, Testing: http://tetamap.wordpress.com > Python, PyPy, pytest contracting: http://merlinux.eu > > > _______________________________________________ > [email protected] > http://codespeak.net/mailman/listinfo/pypy-dev > -- Metaprogramming, Python, Testing: http://tetamap.wordpress.com Python, PyPy, pytest contracting: http://merlinux.eu _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
