Hi Marcos,
On Fri, Oct 16, 2015 at 8:16 PM, Marcos Dione wrote:
> as for the hack itself, it works! \o/ thanks very much for the
> pointers :) Cheers,
No problem. Actually, some Googling finds the very same hack used at
various places and explained in blog posts...
Armin
__
Crud...I think I accidentally sent that twice... :O
I also x-posted this to /r/programming:
https://www.reddit.com/r/programming/comments/3p128a/from_python_to_go_and_back_again_xposted_from/.
On October 16, 2015 3:07:24 PM CDT, Ryan Gonzalez wrote:
>You know how it goes: everyone overhypes som
You know how it goes: everyone overhypes something as "perfect", only to
realize it's not actually perfect.
See: Node.js, Java, Rails, ...
PyPy definitely deserves a bit more use in the real world, so I really like
this presentation.
On October 16, 2015 2:31:32 PM CDT, Tuom Larsen wrote:
>Dea
You know how it goes: everyone overhypes something as "perfect", only to
realize it's not actually perfect.
See: Node.js, Java, Rails, ...
PyPy definitely deserves a bit more use in the real world, so I really like
this presentation.
On October 16, 2015 2:31:32 PM CDT, Tuom Larsen wrote:
>Dea
Dead list,
not sure if this is the right place to share but there is a
presentation by a Mozilla dev being currently discussed on Reddit
where PyPy received quite some praise:
https://www.reddit.com/r/golang/comments/3oztwi/from_python_to_go_and_back_again_mozilla_dev/
Cheers!
__
On Fri, Oct 16, 2015 at 09:07:27AM +0200, Marcos Dione wrote:
> On Fri, Oct 16, 2015 at 08:32:36AM +0200, Armin Rigo wrote:
> > On Thu, Oct 15, 2015 at 4:50 PM, Marcos Dione wrote:
> > >> so I'll keep investigating :-]
> > >
> > > maybe context managers add a stack frame/do something with
On Thu, Oct 15, 2015 at 6:35 PM, Matti Picus wrote:
>
>
> On 15/10/15 20:18, Yury V. Zaytsev wrote:
>
>> Forwarded Message
>> From: David Cournapeau
>> To: Yury V. Zaytsev
>> Subject: Re: [pypy-dev] Building pypy from sources: partial build
>> support ?
>> Date: Thu, 15 Oct 20
I claim at least a part of the jitted code change is a fluke. A part
is due to disabling of retracing, which never worked properly as far
as I know anyway, we'll reenable that somehow at some point. I would
not put it in the release announcement.
On Fri, Oct 16, 2015 at 2:33 PM, Matti Picus wrote
On 16/10/15 15:23, Phyo Arkar wrote:
warmup time improvement of 20% or so at the cost of a minor
regression in jitted code speed.
20% Warmup is huge! That will skyrocket in bencmarks.
But Minor regression? how minor ?
speed.pypy.org (which measures only jit performance without warmup) went
warmup time improvement of 20% or so at the cost of a minor regression in
jitted code speed.
20% Warmup is huge! That will skyrocket in bencmarks.
But Minor regression? how minor ?
On Fri, Oct 16, 2015 at 6:51 PM, Phyo Arkar
wrote:
> So that will work like 15.11 , 15.5 ? something like that?
So that will work like 15.11 , 15.5 ? something like that?
Predefined release cycle ?
And Awesome work Guys!@
On Fri, Oct 16, 2015 at 11:42 AM, Matti Picus wrote:
> I have started a major release cycle, and consensus was to start a new
> numbering scheme, based on yy.mm
>
> While every release
On Fri, Oct 16, 2015 at 08:32:36AM +0200, Armin Rigo wrote:
> On Thu, Oct 15, 2015 at 4:50 PM, Marcos Dione wrote:
> >> so I'll keep investigating :-]
> >
> > maybe context managers add a stack frame/do something with them
> > internally?
>
> Sorry, you're right. Now it seems from lookin
12 matches
Mail list logo
