Re: [pypy-dev] PyPy current status

2014-05-22 Thread Brian Kearns
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 -- t

Re: [pypy-dev] PyPy current status

2014-05-22 Thread David Schneider
Hi Anto, On 22.05.2014, at 09:49, Antonio Cuni 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 answ

Re: [pypy-dev] PyPy current status

2014-05-22 Thread Antonio Cuni
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 t

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Philip Jenvey
On May 20, 2014, at 4:56 PM, Antonio Cuni 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

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Maciej Fijalkowski
7? check out our blog post ;-) On Wed, May 21, 2014 at 5:23 PM, Antonio Cuni 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 :)

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Antonio Cuni
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 :)​ ___ pypy-dev mailing list pypy-dev@python.org https://mail.

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Maciej Fijalkowski
On Wed, May 21, 2014 at 1:56 AM, Antonio Cuni 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://bitbu

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Alex Gaynor
I don't have any good numbers, sorry. On Wed, May 21, 2014 at 1:32 AM, Antonio Cuni wrote: > Hi Alex, > > On Wed, May 21, 2014 at 1:58 AM, Alex Gaynor wrote: > >> Oh, performance, the only Ruby implementation that's competitive with it >> is the Oracle Ruby VM with Truffle, I think they've star

Re: [pypy-dev] PyPy current status

2014-05-21 Thread David Schneider
Hi all, On 21.05.2014, at 01:56, Antonio Cuni 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 comp

Re: [pypy-dev] PyPy current status

2014-05-21 Thread Antonio Cuni
Hi Alex, On Wed, May 21, 2014 at 1:58 AM, Alex Gaynor 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

Re: [pypy-dev] PyPy current status

2014-05-20 Thread Alex Gaynor
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 wrote:

Re: [pypy-dev] PyPy current status

2014-05-20 Thread Alex Gaynor
On Tue, May 20, 2014 at 4:56 PM, Antonio Cuni 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://bi

[pypy-dev] PyPy current status

2014-05-20 Thread Antonio Cuni
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?at=ext