On 05:39 pm, john.m.cam...@gmail.com wrote:
I have been noticing a pattern where many who are writing Python code
to
run on PyPy are relying more and more on using the jitviewer to help
them
write faster code. Unfortunately, many of them who do so don't look at
improving the design of their
On Sun, Feb 3, 2013 at 9:25 PM, exar...@twistedmatrix.com wrote:
On 05:39 pm, john.m.cam...@gmail.com wrote:
I have been noticing a pattern where many who are writing Python code to
run on PyPy are relying more and more on using the jitviewer to help them
write faster code. Unfortunately,
What makes you think people will even read this warning, let alone
prioritize it over their immediate desire to make their program run
faster?
(Not that I am objecting to adding the warning, but I think you might be
fooling yourself if you think it will have any impact)
Jean-Paul
I agree
Let me rephrase it. Where did you look for such a warning and you did
not find it so you assumed it's ok?
Cheers,
fijal
Having a warning on https://bitbucket.org/pypy/jitviewer would be good.
On Sun, Feb 3, 2013 at 3:08 PM, John Camara john.m.cam...@gmail.com wrote:
What makes you
On Sun, Feb 3, 2013 at 10:12 PM, Maciej Fijalkowski fij...@gmail.com wrote:
On Sun, Feb 3, 2013 at 10:08 PM, John Camara john.m.cam...@gmail.com wrote:
What makes you think people will even read this warning, let alone
prioritize it over their immediate desire to make their program run
faster?
On Fri, Feb 1, 2013 at 12:01 AM, John Camara john.m.cam...@gmail.com wrote:
A couple of days ago I heard about the Parallella [1] project which is an
open hardware platform similar to the Raspberry Pi but with much higher
capabilities. It has a Zynq Z-7010 which has both a dual core ARM A9
Also, looking at the msgpack - this code is maybe not ideal, but if
you're dealing with buffer-level protocols, you end up with code
looking like C a lot.
I do agree that this type a code will likely end up looking like C but it's
not necessary for all of it to look like c. Like there should
On Sun, Feb 3, 2013 at 10:29 PM, John Camara john.m.cam...@gmail.com wrote:
Also, looking at the msgpack - this code is maybe not ideal, but if
you're dealing with buffer-level protocols, you end up with code
looking like C a lot.
I do agree that this type a code will likely end up looking
On 04/02/13 06:25, exar...@twistedmatrix.com wrote:
On 05:39 pm, john.m.cam...@gmail.com wrote:
I have been noticing a pattern where many who are writing Python code to
run on PyPy are relying more and more on using the jitviewer to help them
write faster code. Unfortunately, many of them who
On Mon, Feb 4, 2013 at 12:39 AM, Steven D'Aprano st...@pearwood.info wrote:
On 04/02/13 06:25, exar...@twistedmatrix.com wrote:
On 05:39 pm, john.m.cam...@gmail.com wrote:
I have been noticing a pattern where many who are writing Python code to
run on PyPy are relying more and more on using
that is definitely a no (my screen is too small to have some noise
there, if for no other reason), it might have a warning in the
documentation though, if it's any useful. But honestly, I doubt such a
warning makes any sense. People who are capable of using jitviewer
already know better.
I
11 matches
Mail list logo
