Mailman 3 September 2013 - pypy-issue

[issue929] Improve platform support for FreeBSD
by David Naylor Nov. 3, 2013

Nov. 3, 2013

New submission from David Naylor <naylor.b.david(a)gmail.com>: Fix a bug where a custom CFLAGS/LDFLAGS could result in a linker error. On FreeBSD `-pthreads' needs to be passed to the linker so ensure the flags always contains `-pthreads'. While here fully implement the get_env_vector() function. I've notices the other BSDs have copied the freebsd.py platform file, perhaps this patch is relevant for them as well (I, however, have no way to verify this). ---------- files: patch-pypy::translator::platform::freebsd.py messages: 3441 nosy: DragonSA, pypy-issue priority: bug status: unread title: Improve platform support for FreeBSD ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue929> ________________________________________

1 2

[issue532] Disable assert statements with -O flag
by Joost Cassee Oct. 30, 2013

Oct. 30, 2013

New submission from Joost Cassee <joost(a)cassee.net>: The CPython binary uses the -O flag to disable assert statements. PyPy should offer the same behavior. See the IRC log at: http://tismerysoft.de/pypy/irc-logs/pypy/%23pypy.log.20100514 See also for a description of CPython behavior: http://docs.python.org/tutorial/modules.html#compiled-python-files http://docs.python.org/reference/simple_stmts.html#the-assert-statement http://docs.python.org/using/cmdline.html#interface-options ---------- effort: ??? messages: 1724 nosy: jcassee, pypy-issue priority: feature release: ??? status: unread title: Disable assert statements with -O flag _______________________________________________________ PyPy development tracker <pypy-dev-issue(a)codespeak.net> <https://codespeak.net/issue/pypy-dev/issue532> _______________________________________________________

2 1

[issue1548] numpypy ravel() bug
by Dmitrey Oct. 15, 2013

Oct. 15, 2013

New submission from Dmitrey <dmitrey15(a)ukr.net>: >>> from numpy import * >>> ravel(float64(1)) array([ 1.]) >>>> from numpypy import * >>>> ravel(float64(1.0)) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/dmitrey/Install/pypy-c-jit-65418-d49964ac4b2c-linux/lib_pypy/numpypy/core/fromnumeric.py", line 1061, in ravel return a.ravel(order=order) TypeError: ravel() got an unexpected keyword argument 'order' ---------- messages: 5956 nosy: Dmitrey, pypy-issue priority: bug status: unread title: numpypy ravel() bug ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1548> ________________________________________

5 4

[issue1598] Multiplication of np.ndarray with a Python int or float results in loss of dtype
by benma Oct. 8, 2013

Oct. 8, 2013

New submission from benma <mbencun(a)gmail.com>: Hi a = np.array([1,2,3], dtype=np.int16) # outputs dtype('int64') instead of dtype('int16') print (a*2).dtype Same thing happens with floats. dtype is resetted to the default dtype, 64 bits on my machine. numpy on CPython keeps the original dtype. I ran into this bug when I used (a*2) as an input to a C function and the size (in bytes) of each element doubled. Best, Marko ---------- messages: 6143 nosy: benma, pypy-issue priority: bug release: 2.1 status: unread title: Multiplication of np.ndarray with a Python int or float results in loss of dtype ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1598> ________________________________________

2 1

[issue1589] numpy: Structured arrays give odd behavior
by Isaac Freeman Oct. 4, 2013

Oct. 4, 2013

New submission from Isaac Freeman <memotype(a)gmail.com>: I'm running the latest nightly as of last night. Trying to construct structured arrays from a list gives add characters and values in the resulting array: numpypy: In [76]: c = numpy.array([[(1,2,'a'),(3,4,'b')],[(5,6,'c'),(7,8,'d')]], dtype=[('bg', 'i8'), ('fg', 'i8'), ('char', 'S1')] ) In [77]: c Out[77]: '), (3, 4, '')], [(5, 6, ''), (7, 8, '')]], dtype=void136) (There are some non-printable characters in the output.) Compared to numpy in cpython: >>> c = numpy.array([[(1,2,'a'),(3,4,'b')],[(5,6,'c'),(7,8,'d')]], dtype=[('bg', 'i8'), ('fg', 'i8'), ('char', 'S1')]) >>> c array([[(1, 2, 'a'), (3, 4, 'b')], [(5, 6, 'c'), (7, 8, 'd')]], dtype=[('bg', '<i8'), ('fg', '<i8'), ('char', 'S1')]) This also affects array assignment. In numpypy: In [83]: c = numpy.zeros((2,2,2), dtype=[('bg', 'i8'), ('fg', 'i8'), ('char', '\ S1')]) In [84]: c Out[84]: array([[[(0, 0, ''), (0, 0, '')], [(0, 0, ''), (0, 0, '')]], [[(0, 0, ''), (0, 0, '')], [(0, 0, ''), (0, 0, '')]]], dtype=void136) In [85]: c[0,0] = (1, 2, 'a') --------------------------------------------------------------------------- ValueError Traceback (most recent call last) <ipython-input-85-158a9c3d29f8> in <module>() ----> 1 c[0,0] = (1, 2, 'a') ValueError: invalid literal for int() with base 10: 'a' In [86]: And in numpy/cpython: >>> c = numpy.zeros((2,2,2), dtype=[('bg', 'i8'), ('fg', 'i8'), ('char', '\ ... S1')]) >>> c array([[[(0, 0, ''), (0, 0, '')], [(0, 0, ''), (0, 0, '')]], [[(0, 0, ''), (0, 0, '')], [(0, 0, ''), (0, 0, '')]]], dtype=[('bg', '<i8'), ('fg', '<i8'), ('char', 'S1')]) >>> c[0,0] = (1, 2, 'a') >>> c[0,0] array([(1, 2, 'a'), (1, 2, 'a')], dtype=[('bg', '<i8'), ('fg', '<i8'), ('char', 'S1')]) >>> ---------- messages: 6091 nosy: memotype, pypy-issue priority: bug status: unread title: numpy: Structured arrays give odd behavior ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1589> ________________________________________

2 5

[issue1615] pypy cannot build pypy3 errors with SyntaxError
by Greg Czajkowski Sept. 30, 2013

Sept. 30, 2013

New submission from Greg Czajkowski <gregczajkowski(a)yahoo.com>: I am on SUSE10 with HEAD on the repo updated today. pypy and pypy3 successfully build with cpython2.7, but pypy is not able to build pypy3 setenv LD_LIBRARY_PATH /path/libffi/lib:/usr/pkgs/openssl/1.0.1c/lib64 setenv CFLAGS "-D__GNUC__ -D__amd64__ -I /path/libffi/lib/libffi-3.0.13/include -I /usr/pkgs/openssl/1.0.1c/include -I /usr/pkgs/openssl/1.0.1c/openssl" setenv LDFLAGS "-L/path/libffi/lib -L/usr/pkgs/openssl/1.0.1c/lib64 -Wl,-rpath=/usr/pkgs/icc/13.1.3e/composer_xe_2013.5.192/compiler/lib/intel64 -limf -lsvml -lirng -lintlc" /path/pypy/pypy/goal/pypy.2.7-icc-c ../../rpython/bin/rpython --opt=jit --batch --cc=/usr/pkgs/icc/13.1.3e/bin/icc --gcrootfinder=shadowstack targetpypystandalone Traceback (most recent call last): File "app_main.py", line 72, in run_toplevel File "../../rpython/bin/rpython", line 13, in <module> from rpython.translator.goal.translate import main File "/path/pypy/rpython/translator/goal/translate.py", line 89, in <module> log = py.log.Producer("translation") File "/path/pypy/py/_apipkg.py", line 114, in __makeattr result = importobj(modpath, attrname) File "/path/pypy/py/_apipkg.py", line 37, in importobj module = __import__(modpath, None, None, ['__doc__']) File "/path/pypy/py/_log/log.py", line 184, in <module> setattr(Syslog, _prio, getattr(py.std.syslog, _prio)) File "/path/pypy/py/_std.py", line 13, in __getattr__ m = __import__(name) File "/path/pypy/lib_pypy/syslog.py", line 68, in <module> lib = ffi.verify(""" File "/path/pypy/lib_pypy/cffi/api.py", line 309, in verify from .verifier import Verifier, _caller_dir_pycache File "/path/pypy/lib_pypy/cffi/verifier.py", line 1, in <module> import sys, os, binascii, imp, shutil File "/path/pypy/lib-python/2.7/shutil.py", line 21, in <module> from grp import getgrnam File "/path/pypy/lib_pypy/grp.py", line 28 class struct_group(metaclass=_structseq.structseqtype): ^ SyntaxError: invalid syntax Thanks for all the quick help! ---------- messages: 6224 nosy: gcflymoto, pypy-issue priority: bug release: 2.1 status: unread title: pypy cannot build pypy3 errors with SyntaxError ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1615> ________________________________________

3 9

[issue1617] Deleted local variables show up in locals()
by Alex Gaynor Sept. 30, 2013

Sept. 30, 2013

New submission from Alex Gaynor <alex.gaynor(a)gmail.com>: Specifically, if you call locals(), delete a local var, and then call locals() again, it's still present: def main(): a = 3 locals() del a print locals() main() The cause is at pypy/interpreter/eval.py fast2locals:L110 ---------- messages: 6235 nosy: agaynor, pypy-issue priority: bug status: unread title: Deleted local variables show up in locals() ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1617> ________________________________________

1 1

[issue1559] Patch for PyArray_* interface by Stefan Mueller
by mattip Sept. 29, 2013

Sept. 29, 2013

New submission from mattip <matti.picus(a)gmail.com>: merged as pypy-pyarray branch ---------- nosy: +mattip status: unread -> resolved ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1559> ________________________________________

1 0

[issue1616] Tkinter code bug
by Armin Rigo Sept. 28, 2013

Sept. 28, 2013

New submission from Armin Rigo <armin.rigo(a)gmail.com>: lib_pypy/_tkinter/tclobj.py:FromObj: The function above uses the "result" local variable before it is defined, at various places. It crashes e.g. running the following example code: from Tkinter import * tk=Tk() tk.grid_propagate() ---------- messages: 6229 nosy: arigo, pypy-issue priority: bug status: unread title: Tkinter code bug ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1616> ________________________________________

2 2

[issue1606] Test failures
by Armin Rigo Sept. 28, 2013

Sept. 28, 2013

New submission from Armin Rigo <armin.rigo(a)gmail.com>: This is a reminder for various people that there are various tests that have been failing, sometimes for a long time. (I might just go and skip the tests instead, say in 1-2 weeks; which is a bad practice, so I hope you'll do something before.) micronumpy.test.test_dtypes Shows one failure on 32-bit. test_pypy_c.test_thread Just fails. test__pypyjson, test_runicode, test_ucd Showed up recently on tannit32 once we upgraded to a Python 2.7 with sys.maxunicode == 65536. (I may have a look at the last two.) ---------- messages: 6170 nosy: arigo, pypy-issue priority: critical status: unread title: Test failures ________________________________________ PyPy bug tracker <tracker(a)bugs.pypy.org> <https://bugs.pypy.org/issue1606> ________________________________________

1 1