On Sat, Feb 16, 2013 at 10:03 AM, Stefan Behnel wrote:
> Nick Coghlan, 16.02.2013 08:49:
>> Yes, the PyPy team and scientific users of Python have a long history
>> of talking past each other (and abusing each other for the mutual lack
>> of understanding). However, that's no excuse for deliberate
Nick Coghlan, 16.02.2013 08:49:
> Yes, the PyPy team and scientific users of Python have a long history
> of talking past each other (and abusing each other for the mutual lack
> of understanding). However, that's no excuse for deliberately ignoring
> the advantages JIT compilation can bring
No-on
On Sat, Feb 16, 2013 at 5:14 PM, Stefan Behnel wrote:
> Hmm, I don't have the feeling that this discussion is leading anywhere
> (especially not on this list). After all, it's quite possible to fire up a
> PyPy runtime from a CPython runtime and have them talk to each other,
> letting each one do
Steven D'Aprano, 16.02.2013 07:13:
> On 16/02/13 16:41, Stefan Behnel wrote:
>
>>> PyPy is indeed a work in progress in this area, but that doesn't
>>> necessarily preclude it from being included.
>>
>> That may be a matter of POV, but as long as PyPy fails to integrate (and
>> you just called tha
On 16/02/13 16:41, Stefan Behnel wrote:
PyPy is indeed a work in progress in this area, but that doesn't
necessarily preclude it from being included.
That may be a matter of POV, but as long as PyPy fails to integrate (and
you just called that "not a main focus"), I find it hard to defend its
Philip Jenvey, 16.02.2013 01:01:
> On Fri, Feb 15, 2013 at 2:36 PM, Stefan Behnel wrote:
>> So, while I agree that PyPy is worth a try in certain application areas,
>> and can be helpful for some special needs, also in the field of scientific
>> computing, it's lightyears away from a production-rea
Stefan Behnel wrote:
>
> This is off-topic for this list, but the main problem with PyPy is that
> you'll quickly hit a lot of walls when you try to use it for anything
> serious in the area. It's true that there is a certain level of
> interoperability with CPython extensions, but calling it a "fo
On Fri, Feb 15, 2013 at 2:36 PM, Stefan Behnel wrote:
> This is off-topic for this list, but the main problem with PyPy is that
> you'll quickly hit a lot of walls when you try to use it for anything
> serious in the area. It's true that there is a certain level of
> interoperability with CPython
Paul Boddie, 15.02.2013 22:44:
> Travis Oliphant wrote:
>> This page is specifically for Compiler projects that either integrate with
>> or work directly with the CPython run-time which is why PyPy is not
>> presently listed. The PyPy project is a great project but we just felt
>> that we wanted t
Travis Oliphant wrote:
>
> With Numba and Blaze we have been doing a lot of work on what essentially
> is compiler technology and realizing more and more that we are treading on
> ground that has been plowed before with many other projects. So, we
> wanted to create a web-site and perhaps even a
Hey all,
With Numba and Blaze we have been doing a lot of work on what essentially is
compiler technology and realizing more and more that we are treading on ground
that has been plowed before with many other projects. So, we wanted to create
a web-site and perhaps even a mailing list or for
11 matches
Mail list logo
