PyPy current status
Hi all,
I am preparing the usual "PyPy status talk" which I'll give to the upcoming Pycon Italy, which is going to cover what happened in the last two years of PyPy.
If you are interested, the draft slides are here: https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?a...
In the talk, I will to give an overview of the current status of the various subprojects, so I'd be glad if you could help because you surely know better than me the status of the area of your competence :)
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Matti, Brian: what about numpy? Since people like numbers, what percentage of numpy we can consider completed?
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and Hippy. How much complete are they? What are the performance? I know that hippy is still actively developed, but what about Topaz?
Other than what I asked, I'll also highlight CFFI and STM. If anyone has ideas for other cool things which happened in PyPy since 2012, suggestions are welcome :)
thank you very much! Anto
On Tue, May 20, 2014 at 4:56 PM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi all,
I am preparing the usual "PyPy status talk" which I'll give to the upcoming Pycon Italy, which is going to cover what happened in the last two years of PyPy.
If you are interested, the draft slides are here:
https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?a...
In the talk, I will to give an overview of the current status of the various subprojects, so I'd be glad if you could help because you surely know better than me the status of the area of your competence :)
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Matti, Brian: what about numpy? Since people like numbers, what percentage of numpy we can consider completed?
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and Hippy. How much complete are they? What are the performance? I know that hippy is still actively developed, but what about Topaz?
Topaz has almost all Ruby syntax implemented, and many methods/builtin types, but very little of the Ruby stdlib.
I'm no longer actively working on it (at some point I'll write a blog post about that).
Other than what I asked, I'll also highlight CFFI and STM. If anyone has ideas for other cool things which happened in PyPy since 2012, suggestions are welcome :)
thank you very much! Anto
Alex
Oh, performance, the only Ruby implementation that's competitive with it is the Oracle Ruby VM with Truffle, I think they've started merging that into JRuby by now, so I'm not sure how that compares. Definitely faster than MRI though :-)
Alex
On Tue, May 20, 2014 at 4:58 PM, Alex Gaynor alex.gaynor@gmail.com wrote:
On Tue, May 20, 2014 at 4:56 PM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi all,
I am preparing the usual "PyPy status talk" which I'll give to the upcoming Pycon Italy, which is going to cover what happened in the last two years of PyPy.
If you are interested, the draft slides are here:
https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?a...
In the talk, I will to give an overview of the current status of the various subprojects, so I'd be glad if you could help because you surely know better than me the status of the area of your competence :)
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Matti, Brian: what about numpy? Since people like numbers, what percentage of numpy we can consider completed?
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and Hippy. How much complete are they? What are the performance? I know that hippy is still actively developed, but what about Topaz?
Topaz has almost all Ruby syntax implemented, and many methods/builtin types, but very little of the Ruby stdlib.
I'm no longer actively working on it (at some point I'll write a blog post about that).
Other than what I asked, I'll also highlight CFFI and STM. If anyone has ideas for other cool things which happened in PyPy since 2012, suggestions are welcome :)
thank you very much! Anto
Alex
-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084
Hi Alex,
On Wed, May 21, 2014 at 1:58 AM, Alex Gaynor alex.gaynor@gmail.com wrote:
Oh, performance, the only Ruby implementation that's competitive with it is the Oracle Ruby VM with Truffle, I think they've started merging that into JRuby by now, so I'm not sure how that compares. Definitely faster than MRI though :-)
do you have a number to put on the slides? People like hearing "N times faster than X" better than "faster than X" :)
thanks!
I don't have any good numbers, sorry.
On Wed, May 21, 2014 at 1:32 AM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi Alex,
On Wed, May 21, 2014 at 1:58 AM, Alex Gaynor alex.gaynor@gmail.comwrote:
Oh, performance, the only Ruby implementation that's competitive with it is the Oracle Ruby VM with Truffle, I think they've started merging that into JRuby by now, so I'm not sure how that compares. Definitely faster than MRI though :-)
do you have a number to put on the slides? People like hearing "N times faster than X" better than "faster than X" :)
thanks!
Hi all,
On 21.05.2014, at 01:56, Antonio Cuni anto.cuni@gmail.com wrote:
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Regarding ARM, the status is indeed "it just works" (although the JIT lacks a few features compared to x86). For performance the best overview is this blogpost http://morepypy.blogspot.de/2013/05/pypy-20-alpha-for-arm.html from last year, which should still be mostly accurate.
It might be worth pointing out that PyPy is being distributed as part of the Raspbian OS images for the Raspberry-Pi
Cheers
David
Hi David,
thank you for the prompt answer. One more question, since I am sure that people will ask me :). Does PyPy work on android? I suppose the answer is "yes, but of course without integration with the UI", but better to check.
I'll also point that the Rasperry-Pi foundation founded part of the ARM development. It founded also pygame_cffi, right?
On Wed, May 21, 2014 at 2:31 PM, David Schneider david.schneider@bivab.dewrote:
Hi all,
On 21.05.2014, at 01:56, Antonio Cuni anto.cuni@gmail.com wrote:
David: what is the current status of PyPy on ARM? Should I say "it just
works" or there is something more to add? What about performance?
Regarding ARM, the status is indeed "it just works" (although the JIT lacks a few features compared to x86). For performance the best overview is this blogpost http://morepypy.blogspot.de/2013/05/pypy-20-alpha-for-arm.html from last year, which should still be mostly accurate.
It might be worth pointing out that PyPy is being distributed as part of the Raspbian OS images for the Raspberry-Pi
Cheers
David
Hi Anto,
On 22.05.2014, at 09:49, Antonio Cuni anto.cuni@gmail.com wrote:
thank you for the prompt answer. One more question, since I am sure that people will ask me :). Does PyPy work on android? I suppose the answer is "yes, but of course without integration with the UI", but better to check.
The answer is more of a "in theory yes", but besides some small experiments I did at some point, we haven't really tried to build PyPy for android.
I'll also point that the Rasperry-Pi foundation founded part of the ARM development. It founded also pygame_cffi, right?
Yes, they funded the a part of the ARM development (ARMv6 and finishing the JIT), the incremental GC and pygame_cffi AFAIK.
Cheers
David
On Wed, May 21, 2014 at 1:56 AM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi all,
I am preparing the usual "PyPy status talk" which I'll give to the upcoming Pycon Italy, which is going to cover what happened in the last two years of PyPy.
If you are interested, the draft slides are here: https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?a...
In the talk, I will to give an overview of the current status of the various subprojects, so I'd be glad if you could help because you surely know better than me the status of the area of your competence :)
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Matti, Brian: what about numpy? Since people like numbers, what percentage of numpy we can consider completed?
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and Hippy. How much complete are they? What are the performance? I know that hippy is still actively developed, but what about Topaz?
What do you exactly want to know about hippy performance?
7? check out our blog post ;-)
On Wed, May 21, 2014 at 5:23 PM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi,
What do you exactly want to know about hippy performance?
I simply want to put in a slide "hippy is N times faster than standard PHP", for some reasonable value of N. Nothing more :)
On May 20, 2014, at 4:56 PM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi all,
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
We’ll have a release out with 3.2 compatibility that we can consider ‘stable’ shortly. This will include one additional feature from 3.3: support for the u’’ prefix.
Additionally, a 3.3 branch was created last month by Amaury and he's started some of the initial work there.
-- Philip Jenvey
As far as numpy, the last few blog status posts are probably give the best idea:
http://morepypy.blogspot.com/2014/04/numpy-on-pypy-status-update.html http://morepypy.blogspot.com/2014/03/numpy-status-update-february.html
Somewhere in there I mention count of tests passing out of tests total -- that's probably the best, albeit approximate indicator of functionality. You could pull an updated count from the nightly tests:
http://buildbot.pypy.org/builders/numpy-compatability-linux-x86-64
On Tue, May 20, 2014 at 4:56 PM, Antonio Cuni anto.cuni@gmail.com wrote:
Hi all,
I am preparing the usual "PyPy status talk" which I'll give to the upcoming Pycon Italy, which is going to cover what happened in the last two years of PyPy.
If you are interested, the draft slides are here:
https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?a...
In the talk, I will to give an overview of the current status of the various subprojects, so I'd be glad if you could help because you surely know better than me the status of the area of your competence :)
David: what is the current status of PyPy on ARM? Should I say "it just works" or there is something more to add? What about performance?
Matti, Brian: what about numpy? Since people like numbers, what percentage of numpy we can consider completed?
Philip: same question for py3k. Is it still considered beta quality or we can say it's stable?
Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and Hippy. How much complete are they? What are the performance? I know that hippy is still actively developed, but what about Topaz?
Other than what I asked, I'll also highlight CFFI and STM. If anyone has ideas for other cool things which happened in PyPy since 2012, suggestions are welcome :)
thank you very much! Anto
participants (6)
-
Alex Gaynor -
Antonio Cuni -
Brian Kearns -
David Schneider -
Maciej Fijalkowski -
Philip Jenvey