Thanks Maciej,
sys._getframe was introduced by "magicsuper", which I used to avoid refactoring
all super() calls. I've done that now and there shouldn't be any more
sys._getframe calls. You can pull in this commit from the pypy2 branch.
Unfortunately, this didn't improve performance much. PyPy
Hi,
I'm wondering whether there are any plans to port pypy itself to
python 3 at some point. And what the benefits of that might be (other
than having a more recent host language). Is there anything in python
3 that would make it easier/harder for pypy?
Thanks,
Martin
__
Hi Martin,
On 2 March 2014 13:03, Martin Matusiak wrote:
> I'm wondering whether there are any plans to port pypy itself to
> python 3 at some point. And what the benefits of that might be (other
> than having a more recent host language). Is there anything in python
> 3 that would make it easier
Hi Brecht,
On 1 March 2014 23:34, Brecht Machiels wrote:
> While PyPy2 performs better than PyPy3, it's still much slower than CPython.
> Is RinohType hitting a weak spot in PyPy? Any hints on what I can do to
> improve performance?
It's not really helpful, but the warm-up time is the first is
Hi Brecht.
I must say I've been trying to understand what's going on and I'm
failing so far. Thanks for a valuable benchmark! And yes, we're
working on improving the warmup time (ETA unknown though)
On Sun, Mar 2, 2014 at 12:11 PM, Brecht Machiels wrote:
> Thanks Maciej,
>
> sys._getframe was in
