Mailman 3 October 2012 - pypy-dev

[cpyext] how to make use of the weakref callback?
by Stefan Behnel 14 Oct '12

14 Oct '12

Hi, when creating a new weakref using PyWeakref_NewRef(obj, callback), a Python callback function can be registered that is supposed to get called when the weakly referenced object dies. The callback receives a single argument, the weakref object. Now, the weak reference object itself is mostly useless, what is interesting is the object it originally referenced. I tried getting at that object by calling PyWeakref_LockObject(), but that already returns None at that point. PyWeakref_GetObject() is basically just a wrapper around that function and behaves the same. Is there any way to figure out what that object was that has just died when the callback gets called? Stefan

2 2

Re: [pypy-dev] [pypy-commit] pypy default: fix for None in kwargs
by Maciej Fijalkowski 13 Oct '12

13 Oct '12

Did this fail any test? If not, it should come with one. On Sat, Oct 13, 2012 at 9:26 PM, mattip <noreply(a)buildbot.pypy.org> wrote: > Author: mattip <matti.picus(a)gmail.com> > Branch: > Changeset: r58111:e537e0093563 > Date: 2012-10-13 21:26 +0200 > http://bitbucket.org/pypy/pypy/changeset/e537e0093563/ > > Log: fix for None in kwargs > > diff --git a/pypy/module/micronumpy/interp_numarray.py b/pypy/module/micronumpy/interp_numarray.py > --- a/pypy/module/micronumpy/interp_numarray.py > +++ b/pypy/module/micronumpy/interp_numarray.py > @@ -661,7 +661,7 @@ > raise operationerrfmt(space.w_ValueError, "Unknown order: %s", > order) > if isinstance(w_object, W_NDimArray): > - if (not space.is_w(w_dtype, space.w_None) and > + if (not space.is_none(w_dtype) and > w_object.get_dtype() is not w_dtype): > raise OperationError(space.w_NotImplementedError, space.wrap( > "copying over different dtypes unsupported")) > _______________________________________________ > pypy-commit mailing list > pypy-commit(a)python.org > http://mail.python.org/mailman/listinfo/pypy-commit

1 0

Weird C code in crashing code line
by Stefan Behnel 12 Oct '12

12 Oct '12

Hi, I get a crash in lxml's test suite on 64bit Linux, right with the first test. I couldn't investigate it in depth so far, but at least I found that it crashes in line 606 of obmalloc.c, which reads as follows: 583 block *bp; [...] 604 bp = pool->freeblock; 605 assert(bp != NULL); 606 if ((pool->freeblock = *(block **)bp) != NULL) { The cast looks a bit smelly to me. Could someone who knows that code please take a look to see if it makes any sense? This kind of code tends to hint at potential aliasing problems to me etc. OTOH, "bp" holds the value 0xc here when it crashes, so there's clearly something going wrong. Here is the stack trace I get: #0 PyObject_Malloc (nbytes=16) at .../pypy/translator/c/src/obmalloc.c:606 #1 0x0000000000eeb938 in pypy_g__ll_malloc_varsize_no_length_zero__Signed_Signed (l_length_1494=<value optimized out>, l_v1845914=<value optimized out>, l_itemsize_9=<value optimized out>) at rpython_memory_gctransform_transform.c:249 #2 0x0000000000cad374 in pypy_g_BaseCpyTypedescr_allocate (l_self_67=0x1aafeb8, l_w_type_11=0x1702040, l_itemcount_7=0) at module_cpyext_pyobject.c:3190 #3 0x0000000000cadc92 in pypy_g_create_ref (l_w_obj_2087=0x7f0d25d49ac0, l_itemcount_1=<value optimized out>) at module_cpyext_pyobject.c:1275 #4 0x0000000000cace27 in pypy_g_make_ref (l_w_obj_2086=0x168de00) at module_cpyext_pyobject.c:509 #5 0x0000000001040796 in PyWeakref_NewRef (l_v2078649=<value optimized out>, l_v2078623=0x0) at module_cpyext_api_2.c:38330 #6 0x00007f0d2576df72 in __pyx_f_4lxml_5etree__registerProxy () from .../lxml-3.0/src/lxml/etree.pypy-19.so #7 0x00007f0d257a361f in __pyx_f_4lxml_5etree__elementFactory () from .../lxml-3.0/src/lxml/etree.pypy-19.so #8 0x00007f0d2578f2cf in __pyx_f_4lxml_5etree_9_Document_getroot () from .../lxml-3.0/src/lxml/etree.pypy-19.so #9 0x00007f0d257c2990 in __pyx_pf_4lxml_5etree_22fromstring () from .../lxml-3.0/src/lxml/etree.pypy-19.so #10 0x00007f0d257c2847 in __pyx_pw_4lxml_5etree_23fromstring () from .../lxml-3.0/src/lxml/etree.pypy-19.so Note that this isn't using the latest nightly PyPy from the buildbot (58001) but I quickly tested it with that as well and it seems to crash at the same place. When I skip the first test, the test suite runs without crashes, so if there isn't something obviously wrong in the code above, I'd see when I find the time to figure out why this particular set of doctests (in test_autolink.txt) crashes but the rest doesn't, even though the etree part of the stack trace above should be the same in a pretty large part of the test suite. Stefan

6 7

failure in SymPy's test suite, isprime gives RPython AssertionError
by Julien Rioux 09 Oct '12

09 Oct '12

Hi, Running sympy's test suite would be a good test for pypy. Sympy is a python module for symbolic mathematics (www.sympy.org). The release 0.7.2 is being prepared and there is a single test failure remaining when running under pypy nightly (from a couple days ago). It boils down to this small example: dirac:~/git/sympy $ cat test_arnault.py from sympy.ntheory import isprime # Arnault's number a = int(''' 803837457453639491257079614341942108138837688287558145837488917522297\ 427376533365218650233616396004545791504202360320876656996676098728404\ 396540823292873879185086916685732826776177102938969773947016708230428\ 687109997439976544144845341155872450633409279022275296229414984230688\ 1685404326457534018329786111298960644845216191652872597534901''') print type(a) print a print isprime(a) dirac:~/git/sympy $ python test_arnault.py <type 'long'> 8038374574536394912570796143419421081388376882875581458374889175222974273765333652186502336163960045457915042023603208766569966760987284043965408232928738791850869166857328267761771029389697739470167082304286871099974399765441448453411558724506334092790222752962294149842306881685404326457534018329786111298960644845216191652872597534901 True dirac:~/git/sympy $ python -V Python 2.7.2 dirac:~/git/sympy $ pypy test_arnault.py <type 'long'> 8038374574536394912570796143419421081388376882875581458374889175222974273765333652186502336163960045457915042023603208766569966760987284043965408232928738791850869166857328267761771029389697739470167082304286871099974399765441448453411558724506334092790222752962294149842306881685404326457534018329786111298960644845216191652872597534901 RPython traceback: File "objspace_std_longobject.c", line 4316, in pow__Long_Long_Long File "rlib_rbigint.c", line 23606, in rbigint_pow Fatal RPython error: AssertionError Aborted dirac:~/git/sympy $ pypy --version Python 2.7.3 (7f6d5c878b908afec8a643b6d6166dfbd0af2bdf, Oct 03 2012, 11:42:40) [PyPy 1.9.1-dev0 with GCC 4.6.2] This code (isprime) is part of previous sympy releases, and this failure did not happen with pypy 1.9 but happens with the nightly from Oct 3 (self built with translate.py -Ojit). Can anyone reproduce? Thanks, Cheers, Julien

3 4

PyPy STM
by Russel Winder 05 Oct '12

05 Oct '12

Armin, Sarah and I are restarting our work on CSP, and extending to creating actors and a dataflow library. It would be good to make this work on Jython, IronPython and PyPy as well as CPython. However we want to get away from a reliance on multiprocessing since it is rather heavyweight for the sort of parallelism we are after. STM as an infrastructure layer in PyPy and CPython would get us away from the GIL and allow for using Python threads bound to kernel threads to allow a single Python process to allow us to create lighweight processes (no application level shared memory). Is the STM variant of PyPy and/or CPython in any form of usable state? If so then we can investigate building from source for ourselves so as to use it as a foundation for building the higher abstraction parallelism for applications programmers. Thanks. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder

6 12

Re: [pypy-dev] Research with PyPy Translation Toolchain
by Adam R. Smith 04 Oct '12

04 Oct '12

Is there any documentation available on what RPython consists of? I can't seem to find a manual. On Thu, Oct 4, 2012 at 4:05 PM, Maciej Fijalkowski <fijall(a)gmail.com> wrote: > On Thu, Oct 4, 2012 at 8:17 PM, Adam R. Smith <smith195(a)illinois.edu> > wrote: > > I am a PhD candidate at the University of Illinois. I am interested in > > learning more about how to use the PyPy Translation Toolchain as part of > a > > research project. We would like to write some code in Python and > generate C > > code from that. When using the Translation Toolchain, a *.c source file > is > > generated and then compiled with GCC. How do I find where the source > files > > are stored before GCC is called? I want to interface with those *.c > files. > > > > Adam Smith > > Ph.D. Candidate > > University of Illinois at Urbana-Champaign > > Hi Adam > > Note that PyPy translation toolchain does not compile Python. It > compiles RPython, which is a restricted subset of Python. However, we > have a Python interpreter written in rPython. >

2 1

Research with PyPy Translation Toolchain
by Adam R. Smith 04 Oct '12

04 Oct '12

I am a PhD candidate at the University of Illinois. I am interested in learning more about how to use the PyPy Translation Toolchain as part of a research project. We would like to write some code in Python and generate C code from that. When using the Translation Toolchain, a *.c source file is generated and then compiled with GCC. How do I find where the source files are stored before GCC is called? I want to interface with those *.c files. Adam Smith Ph.D. Candidate University of Illinois at Urbana-Champaign

3 2