Mailman 3 December 2019 - pypy-issue

Issue #3094: sys.setrecursionlimit(int(10e8)) results in MemoryError since 7.2 release. (pypy/pypy)
by Chris Withers 22 Jan '20

22 Jan '20

New issue 3094: sys.setrecursionlimit(int(10e8)) results in MemoryError since 7.2 release. https://bitbucket.org/pypy/pypy/issues/3094/syssetrecursionlimit-int-10e8-r… Chris Withers: The tests for the mock backport have started failing on pypy since this release, for both 2.7 and 3.6: [https://circleci.com/gh/testing-cabal/mock/3099](https://circleci.com/gh/te… [https://circleci.com/gh/testing-cabal/mock/3093](https://circleci.com/gh/te… ``` def test_copy(self): current = sys.getrecursionlimit() self.addCleanup(sys.setrecursionlimit, current) # can't use sys.maxint as this doesn't exist in Python 3 > sys.setrecursionlimit(int(10e8)) E MemoryError ``` What would be the recommended way to fix this?

2 1

Issue #3139: Tracing of decorated functions has changed between 7.2.0 and 7.3.0 (pypy/pypy)
by Ned Batchelder 31 Dec '19

31 Dec '19

New issue 3139: Tracing of decorated functions has changed between 7.2.0 and 7.3.0 https://bitbucket.org/pypy/pypy/issues/3139/tracing-of-decorated-functions-… Ned Batchelder: The line numbers compiled into code objects has changed for decorated functions In 7.2.0, the def line was included for decorated functions. In 7.3.0, the def line is not included. Decorated methods include the def line in all versions. CPython has always included the def line for decorated functions. For decorated methods, they changed in 3.8 to include the def line for decorated methods also. CPython changed their behavior in Python 3.8 to include the def line for methods, but not functions. ``` $ cat decorators.py # 1 @foo(3) @bar def func(x, y=5): return 6 class Foo: '''9''' @foo def __init__(self): '''12''' return 13 @foo( 16, 17, ) def meth(self): return 20 @foo( 23 ) def func(x=25): return 26 $ /usr/local/pythonz/pythons/PyPy3-v7.2.0/bin/pypy3 -m dis decorators.py 3 0 LOAD_NAME 0 (foo) 2 LOAD_CONST 0 (3) 4 CALL_FUNCTION 1 4 6 LOAD_NAME 1 (bar) 5 8 LOAD_CONST 1 (5) 10 BUILD_TUPLE 1 12 LOAD_CONST 2 (<code object func at 0x000000010a7b76e8, file "decorators.py", line 3>) 14 LOAD_CONST 3 ('func') 16 MAKE_FUNCTION 1 18 CALL_FUNCTION 1 20 CALL_FUNCTION 1 22 STORE_NAME 2 (func) 8 24 LOAD_BUILD_CLASS 26 LOAD_CONST 4 (<code object Foo at 0x000000010a7b7970, file "decorators.py", line 8>) 28 LOAD_CONST 5 ('Foo') 30 MAKE_FUNCTION 0 32 LOAD_CONST 5 ('Foo') 34 CALL_FUNCTION 2 36 STORE_NAME 3 (Foo) 22 38 LOAD_NAME 0 (foo) 23 40 LOAD_CONST 6 (23) 42 CALL_FUNCTION 1 25 44 LOAD_CONST 7 (25) 46 BUILD_TUPLE 1 48 LOAD_CONST 8 (<code object func at 0x000000010a7b7a48, file "decorators.py", line 22>) 50 LOAD_CONST 3 ('func') 52 MAKE_FUNCTION 1 54 CALL_FUNCTION 1 56 STORE_NAME 2 (func) 58 LOAD_CONST 9 (None) 60 RETURN_VALUE $ /usr/local/pythonz/pythons/PyPy3-v7.3.0/bin/pypy3 -m dis decorators.py 3 0 LOAD_NAME 0 (foo) 2 LOAD_CONST 0 (3) 4 CALL_FUNCTION 1 4 6 LOAD_NAME 1 (bar) 8 LOAD_CONST 1 ((5,)) 10 LOAD_CONST 2 (<code object func at 0x000000010bc93e80, file "decorators.py", line 3>) 12 LOAD_CONST 3 ('func') 14 MAKE_FUNCTION 1 16 CALL_FUNCTION 1 18 CALL_FUNCTION 1 20 STORE_NAME 2 (func) 8 22 LOAD_BUILD_CLASS 24 LOAD_CONST 4 (<code object Foo at 0x000000010bcd41d0, file "decorators.py", line 8>) 26 LOAD_CONST 5 ('Foo') 28 MAKE_FUNCTION 0 30 LOAD_CONST 5 ('Foo') 32 CALL_FUNCTION 2 34 STORE_NAME 3 (Foo) 22 36 LOAD_NAME 0 (foo) 23 38 LOAD_CONST 6 (23) 40 CALL_FUNCTION 1 42 LOAD_CONST 7 ((25,)) 44 LOAD_CONST 8 (<code object func at 0x000000010bcd42a8, file "decorators.py", line 22>) 46 LOAD_CONST 3 ('func') 48 MAKE_FUNCTION 1 50 CALL_FUNCTION 1 52 STORE_NAME 2 (func) 54 LOAD_CONST 9 (None) 56 RETURN_VALUE ``` ‌

1 0

Issue #3138: `space.eq_w` and NaN (pypy/pypy)
by Yannick Jadoul 30 Dec '19

30 Dec '19

New issue 3138: `space.eq_w` and NaN https://bitbucket.org/pypy/pypy/issues/3138/spaceeq_w-and-nan Yannick Jadoul: Investigating the failure of a test in `lib-python/3/test/test_array.py`, I noticed that the only reason it’s only failing on the `py3.7` branch is because the test $comparing two `array.array`s containing each one `float('nan')`$ was added in CPython 3.7 \(see [https://bugs.python.org/issue24700](https://bugs.python.org/issue24700) & [https://github.com/python/cpython/pull/3009](https://github.com/python/cpyt…). The same bug is present in `py3.6` and `default`. Even more worryingly, the problem seems to be that `space.eq_w` is used in `pypy/module/array/interp_array.py`'s function `compare_arrays`: ‌ ```python # ... if comp_op == EQ: res = space.eq_w(w_elem1, w_elem2) if not res: return space.w_False elif comp_op == NE: res = space.is_true(space.ne(w_elem1, w_elem2)) if res: return space.w_True # ... ``` ‌ When `space.eq_w(w_elem1, w_elem2)` is replaced by `space.is_true(space.eq(w_elem1, w_elem2))`, the test succeeds, and the two `array.array`s of one NaN are not compared to be equal anymore. The problem seems to be that `space.eq_w` is defined as `return self.is_w(w_obj1, w_obj2) or self.is_true(self.eq(w_obj1, w_obj2))`, and that the evalutation of `is` works as a shortcut for most types and instances, but not for NaN `float`s or classes that define a weird kind of equality operator. Rather than fixing `array.array` by replacing `eq_w(...)` with `is_true(eq(...))`, I thought I’d report the issue, as this might affect a whole bunch of other things?

1 0

Issue #3137: SystemError/internal exception in PyPy3 7.3 (pypy/pypy)
by Vilhjálmur Thorsteinsson 28 Dec '19

28 Dec '19

New issue 3137: SystemError/internal exception in PyPy3 7.3 https://bitbucket.org/pypy/pypy/issues/3137/systemerror-internal-exception-… Vilhjálmur Thorsteinsson: When I run my code on the released PyPy3 7.3, I get the following internal exception and traceback: ‌ ``` RPython traceback: File "pypy_interpreter.c", line 37221, in BuiltinCode_funcrun_obj File "implement_1.c", line 13304, in BuiltinActivation_UwS_W_UnicodeObject_ObjSpace_W File "pypy_interpreter_2.c", line 5947, in newlist_utf8 2019-12-28 12:36:31,989 WARNING:[0] Exception when parsing article at https://mbl.is/frettir/erlent/2019/12/25/genarannsoknir_til_bjargar_simpons…: SystemError('unexpected internal exception (please report a bug): <CheckError object at 0x423d6c0>; internal traceback was dumped to stderr',) ``` This is a regression from 7.2.

1 0

Issue #3136: os.putenv crashes in case of errors (win32) (pypy/pypy)
by Christoph Reiter 25 Dec '19

25 Dec '19

New issue 3136: os.putenv crashes in case of errors (win32) https://bitbucket.org/pypy/pypy/issues/3136/osputenv-crashes-in-case-of-err… Christoph Reiter: ``` import os while 1: os.putenv("==", "foo") ``` On Windows 10 using PyPy 3 7.3.0rc3: no exception raised, process crashes On Windows 10 using CPython 3.8.1: ``` ValueError: illegal environment variable name ``` ‌

1 0

Issue #3135: Compiler warnings when translating (pypy/pypy)
by mattip 24 Dec '19

24 Dec '19

New issue 3135: Compiler warnings when translating https://bitbucket.org/pypy/pypy/issues/3135/compiler-warnings-when-translat… mattip: There are many warnings when translating. ‌ This one $one example of tens of such warnings$ ``` [platform:WARNING] rpython_rlib_4.c: In function ‘pypy_g_TimSort_merge_collapse_13’: [platform:WARNING] /<path>/pypy/rpython/translator/c/src/int.h:32:30: warning: assuming \ signed overflow does not occur when assuming that (X - c) <= X is always true \ [-Wstrict-overflow] [platform:WARNING] #define OP_INT_LT(x,y,r) r = ((x) < (y)) [platform:WARNING] rpython_rlib_4.c:9390:4: note: in expansion of macro ‘OP_INT_LT’ [platform:WARNING] OP_INT_LT(l_index_11327, l_v2221820, l_v2221848); ``` is strange. All the values are `Signed` which is `long`. When I try to [replicate with godbolt](https://godbolt.org/z/u-cBQw), I do not get that warning We also discard `const` qualifiers when accessing a struct field: ``` platform:WARNING] pypy_module_time.c: In function ‘pypy_g__init_timezone’: [platform:WARNING] pypy_module_time.c:370:11: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] [platform:WARNING] l_cp_134 = RPyField(l_res_2143, tm_zone); ``` There are many more warnings, but these overshadow the other warnings.

1 0

Issue #3134: pypy3+Windows: Non-ASCII filenames broken (pypy/pypy)
by Christoph Reiter 23 Dec '19

23 Dec '19

New issue 3134: pypy3+Windows: Non-ASCII filenames broken https://bitbucket.org/pypy/pypy/issues/3134/pypy3-windows-non-ascii-filenam… Christoph Reiter: ```python import os fn = 'öäü.mp3' with open(fn, 'wb'): assert os.path.exists(fn) ``` Works with Python 3, fails with PyPy 3 on Windows 10. The file gets creates with PyPy3 though, even with the right name. ‌

1 0

Issue #3133: ctypes: surrogate pairs in unicode buffer not merged (pypy/pypy)
by Christoph Reiter 23 Dec '19

23 Dec '19

New issue 3133: ctypes: surrogate pairs in unicode buffer not merged https://bitbucket.org/pypy/pypy/issues/3133/ctypes-surrogate-pairs-in-unico… Christoph Reiter: ``` buf = ctypes.create_unicode_buffer(2) buf[0] = "\ud800" buf[1] = "\udc01" assert buf[:] == '\U00010001' ``` Works in CPython 3, fails with PyPy 3 ‌

1 0

Issue #3132: pypy3: utf-16 + surrogatepass doesn't error out on invalid input (pypy/pypy)
by Christoph Reiter 23 Dec '19

23 Dec '19

New issue 3132: pypy3: utf-16 + surrogatepass doesn't error out on invalid input https://bitbucket.org/pypy/pypy/issues/3132/pypy3-utf-16-surrogatepass-does… Christoph Reiter: `b"\xd8=a".decode("utf-16-be", "surrogatepass")` Expected: `UnicodeDecodeError: 'utf-16-be' codec can't decode byte 0x61 in position 2: truncated data` Actual: No error, wrong result returned. ‌

1 0

Issue #3131: scipy 1.4+ install: error: ‘PyModule_AddFunctions’ was not declared in this scope (pypy/pypy)
by Jan Vesely 22 Dec '19

22 Dec '19

New issue 3131: scipy 1.4+ install: error: ‘PyModule_AddFunctions’ was not declared in this scope https://bitbucket.org/pypy/pypy/issues/3131/scipy-14-install-error Jan Vesely: updating scipy to 1.4 results in: ``` /var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/distutils/system_info.py:664: UserWarning: Specified path /var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/__init__.py/include is invalid. return self.get_paths(self.section, key) /var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/distutils/system_info.py:664: UserWarning: Specified path /usr/local/include/include is invalid. return self.get_paths(self.section, key) /var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/distutils/system_info.py:664: UserWarning: Specified path /usr/include/include is invalid. return self.get_paths(self.section, key) /var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/distutils/system_info.py:664: UserWarning: Specified path /home/user/pypy3-venv/include/include is invalid. return self.get_paths(self.section, key) error: Command "g++ -pthread -fPIC -DPOCKETFFT_PTHREADS -I/home/user/pypy3-venv/include/site/python3.6 -I/home/user/pypy3-venv/include/site/python3.6 -I/var/tmp/pip-build-env-q588n5yp/overlay/site-packages/numpy/core/include -I/home/user/pypy3-venv/include -I/usr/lib/pypy3.6/include -c scipy/fft/_pocketfft/pypocketfft.cxx -o build/temp.linux-x86_64-3.6/scipy/fft/_pocketfft/pypocketfft.o -MMD -MF build/temp.linux-x86_64-3.6/scipy/fft/_pocketfft/pypocketfft.o.d -std=c++14 -fvisibility=hidden" failed with exit status 1 scipy/fft/_pocketfft/pypocketfft.cxx: In function ‘void pybind11_init_pypocketfft(pybind11::module&)’: scipy/fft/_pocketfft/pypocketfft.cxx:731:3: error: ‘PyModule_AddFunctions’ was not declared in this scope 731 | PyModule_AddFunctions(m.ptr(), good_size_meth); | ^~~~~~~~~~~~~~~~~~~~~ scipy/fft/_pocketfft/pypocketfft.cxx: In function ‘void pybind11_init_pypocketfft(pybind11::module&)’: scipy/fft/_pocketfft/pypocketfft.cxx:731:3: error: ‘PyModule_AddFunctions’ was not declared in this scope 731 | PyModule_AddFunctions(m.ptr(), good_size_meth); ``` the attached log is for: ``` $ pypy3 --version Python 3.6.9 (5da45ced70e515f94686be0df47c59abd1348ebc, Nov 02 2019, 18:56:40) [PyPy 7.2.0 with GCC 8.3.0] ``` but the same problem appears in: ```shell $ python --version Python 3.7.4 (47c4c0ed3274, Dec 20 2019, 17:37:49) [PyPy 7.3.0-alpha0 with GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] ``` and: ``` $ python --version Python 3.6.9 (574325fb0c26, Dec 20 2019, 17:38:07) [PyPy 7.3.1-alpha0 with GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] ``` scipy 1.3.x works OK. ‌

1 0