On 23/03/17 12:46, Armin Rigo wrote:
Hi Phyo,
On 21 March 2017 at 05:53, Phyo Arkar wrote:
Teating. Saw warning that it is much slower than pypy2? How much slower?
This warning should be removed or at least made much less strong. We
didn't measure, but it passes many of the same tests for J
Hi all,
https://bitbucket.org/pypy/pypy/issues/2508/dictionary-pop-with-default-fails-with
This is a core regression found by Jason and fixed by Alex Gaynor.
Thanks to both! Is this justification enough to plan a 5.7.1 release
soon?
A bientôt,
Armin.
__
Hi Phyo,
On 21 March 2017 at 05:53, Phyo Arkar wrote:
> Teating. Saw warning that it is much slower than pypy2? How much slower?
This warning should be removed or at least made much less strong. We
didn't measure, but it passes many of the same tests for JIT-code
quality now. Where did we leav
Hi,
On 20 March 2017 at 23:37, Manuel Jacob wrote:
> I'd like to remove cpyext.load_module() on both default and py3.5.
If you're talking about the app-level function, it doesn't seem to be
called at all (at least on default) apart from
test_cpyext.AppTestApi.test_load_error.
A bientôt,
Armin
On Thu, 23 Mar 2017 at 9:42 am, Gelin Yan wrote:
> Hi All
>
> I built pypy 2 5.7 from the source on Ubuntu 14.04 and installed
> numpy 1.12.1 via pip. When running numpy.test('full'), I noticed there was
> a segfault.
>
> I tested pypy 2 5.6 with numpy 1.12.1 too. I didn't see any segfa
Hi All
I built pypy 2 5.7 from the source on Ubuntu 14.04 and installed numpy
1.12.1 via pip. When running numpy.test('full'), I noticed there was a
segfault.
I tested pypy 2 5.6 with numpy 1.12.1 too. I didn't see any segfault.
Regards
gelin yan
__
