Mailman 3 July 2007 - pypy-dev

expected_extra_mallocs
by Simon Burton 20 Jul '07

20 Jul '07

Here is a little test: def func(): x = 1. print x def test_1(): from pypy.translator.c.test.test_genc import compile _func = compile(func, []) _func() I get this error: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ def checking_fn(*args, **kwds): if 'expected_extra_mallocs' in kwds: expected_extra_mallocs = kwds.pop('expected_extra_mallocs') else: expected_extra_mallocs = 0 res = compiled_fn(*args, **kwds) mallocs, frees = module.malloc_counters() E assert mallocs - frees == expected_extra_mallocs > assert (6 - 5) == 0 [/home/simon/local/pypy-latest/pypy/translator/c/test/test_genc.py:54] So, do I call this with expected_extra_mallocs=1 ? In general, how many extra mallocs should I expect ? Simon.

2 1

Re: [pypy-dev] Sprint report
by Laura Creighton 18 Jul '07

18 Jul '07

In a message of Wed, 18 Jul 2007 11:54:49 +0200, Maciek Fijalkowski writes: >Three guys who's names Jacob doesn't remember were working on flex >backend (reusing JavaScript one to be able to produce flex code and some >libraries). I've got no idea what was their progress (hopefully they're >reading pypy-dev and are able to reply :-) > >Cheers, >fijal I think they were René Dudfield, Alejandro Curia and Lucio Torre, from Australia, Argentina and Argentina, who may not be home yet. Laura

1 0

Sprint report
by Jacob Hallén 18 Jul '07

18 Jul '07

I think this got stuck in moderation, as I sent it with a from address that didn't match my mailinglist subscription. Justas, Arlo Belshee and I worked on Python 2.5 compliance. We started with the "with" statement and fairly quickly found that it seemed to work as intended, except for the fact that the necessary "from __future__ import with_statement" had no effect. To make this work properly, we decided to make a clean implementation - CPython does nasty things in order to avoid modifying the AST on the fly. This required modifying the grammar, which in turn led to the discovery that building a parser from the grammar lacked unit tests. We then created the neccessary test setup and made tests for the modifications we were making for the grammar. Then we went on to being able to insert a rule for the "with" statement into the builder on the fly. This required more instrumentation for unit testing and some modifications to the builder. Finally, added a config option to allow selecting different versions from the command line. This was essentially finished, though there may still be places which have the Pthon version hard coded. Jacob

2 1

More sprint reporting
by Jacob Hallén 17 Jul '07

17 Jul '07

Here is what I know happened in other groups: Armin and Laura worked on rffi. After 2 days of trying different approaches and getting stumped each time, they made a breakthrough on Saturday, and managed to produce a fairly complete slution in a matter of a few hours. Making the solution more complete would require a rewrite of ctypes (Ick!). Maciek worked on getting PyPy to be self hosting under pypy-c. This succeeded before he left the sprint. Jakub worked on more scheme features. With the help of Antonio, he managed to get quite a bit done. Exactly what he did, I don't know. Christian worked on fixing pickling of tasklets. He got as far as understanding what the real problem was before I left. Michael and Samuele worked on malloc cleanup. I think they were fairly satisfied with the result. Samuele found and fixed a very nasty bug somewhere in the translator toolchain. Exception transformation was dependent on the order the graphs were evaluated. The result was that exceptions could be lost without a trace. There were 3 people who's names I have forgotten who worked on better documentation on how to leverage the javascript backend. There were some results checked in, but I don't know how complete it is. I think Holger did some work on improving py.test. That was at least his plan, but I never got a chance to ask what he actually did. I think that is about it. Jacob

2 1

revision 45089
by Simon Burton 17 Jul '07

17 Jul '07

I found that revision 45089 makes compilation much slower. No idea why. Simon. ------------------------------------------------------------------------ r45089 | justas | 2007-07-14 08:35:59 -0700 (Sat, 14 Jul 2007) | 8 lines (Arlo, Justas) Introduce --pyversion option to select the parser/compiler grammar Defaults to 2.4, also accepts 2.3 and 2.5a. Changed a bunch of imports to use the selected grammar. TODO: pypy/interpreter/pyparser/symbol.py uses a fixed list of symbols, and it shouldn't

2 1

Taking pypy for a test drive
by Greg Bowyer 13 Jul '07

13 Jul '07

Sorry if this is an exceptional newbie post ... Now that pypy has hit v1 I have tried using it for a few test examples, most of this stuff so far is a little bit simple, however one test is to run a django application that I am developing for someone with pypy rather that cpython However when I fire up pypy i get the following from the django application, what am I missing here greg@gregslaptop ~/projects/minesite/minesite $ ./pypy-c manage.py runserver debug: WARNING: library path not found, using compiled-in sys.path Traceback (most recent call last): File "?", line 32, in run_toplevel File "manage.py", line 11, in <module> execute_manager(settings) File "/usr/lib/python2.4/site-packages/django/core/management.py", line 1736, in execute_manager execute_from_command_line(action_mapping, argv) File "/usr/lib/python2.4/site-packages/django/core/management.py", line 1626, in execute_from_command_line translation.activate('en-us') File "/usr/lib/python2.4/site-packages/django/utils/translation/__init__.py", line 66, in activate return real_activate(language) File "/usr/lib/python2.4/site-packages/django/utils/translation/__init__.py", line 29, in delayed_loader from django.conf import settings File "/usr/lib/python2.4/site-packages/django/conf/__init__.py", line 149, in <module> __builtins__['_'] = first_time_gettext TypeError: cannot set items on object

3 2

Win32 tester
by Scott Dial 13 Jul '07

13 Jul '07

Greetings Everyone, I am going to have to stop running the win32 test suite. I am not sure there is anyone actively correcting problems on win32, so it may be of no consequence. If someone else is interested in running this, then I would be more than glad to share my knowledge with them. Otherwise, sorry to leave you without. -Scott -- Scott Dial scott(a)scottdial.com scodial(a)cs.indiana.edu

3 2

Quick personal view regarding js interpreter
by Maciek Fijalkowski 11 Jul '07

11 Jul '07

It's completely unusable. Usually you end up with Fatal RPythonError in case you try to run stuff. This is not how we go about stuff! All error reporting should work well not only on top of js_interactive, but actually on top of js-c as well. Leonardo - have you even run js_interactive once before you commit? Last time it was unbound local or so. Cheers, fijal :.

1 0

paper on runtime specialization
by Carl Friedrich Bolz 09 Jul '07

09 Jul '07

Hi all! Today I found this rather interesting paper on runtime specialization of C: http://www.cs.washington.edu/research/dyncomp/Papers/tr-97-03-03-abstract.h… I have only skimmed it so far, but it seems there are many shared ideas between PyPy and this approach. Cheers, Carl Friedrich

1 1

select/test_readable on Win32 blocks forever
by Scott Dial 05 Jul '07

05 Jul '07

Greetings, I haven't figured this one out. As the subject says, test_readable for the select module gets stuck forever. If I trust the history of the bot, then it appeared somewhere after r44639 and before r44646. I've looked through the revisions and nothing jumped out at me.. happy hunting to someone more aware of the changes. -Scott -- Scott Dial scott(a)scottdial.com scodial(a)cs.indiana.edu

2 1