Mailman 3 January 2005 - pypy-dev

Re: [pypy-dev] Running Python in reverse
by Alexander Schliep 11 Jan '05

11 Jan '05

On Fri, 7 Jan 2005 hpk(a)trillke.net (holger krekel) wrote: > ... > Yes, i see the problem. At EuroPython 2004 there also was Michael Salib > who also presented his wish to have a "time warp" debugger that allows > to arbitrarily move within execution time of your program and see all > the state. And IIRC, we have been discussing this between PyPy developers This sounds like the same general idea. > ... > Rightfully so. I wouldn't call it "run backwards" though but to jump > arbitrarily in execution and object states. The visualization would look like running backwards; technically you are correct. > Yes, although for debugging in general there is the problem of > "side effects" like dealing with files & sockets, databases etc.pp. Fortunately, this is not a problem for me. > Well, the question is if we could tackle the "History Space" (working > title) at some sprint and you would attend and we would together incorporate It will be really difficult for me to attend sprints, I already travel way too much. I'd be glad though to start to code towards extending Gato. Does it make it a lot of sense to run the whole tkinter app in pypy, or would we just have an embedded pypy-interpreter for the algorithm? Do you have suggestions how to setup the whole thing? Right now I just execfile the algorithm under debugger control. The algorihms calls the visualisation commands as side effects when doing interesting stuff (put a vertex on a queue). The debugger calls the idle_task etc. to keep the GUI alive, whenever something happens. > the functionality into your application for the fun of it. I imagine > a "time slider" that you can arbitrarily move forward and backward > ... Basically like VCR controls. I'd add "run backwards" or so. Best, Alexander

2 1

Common Lisp translation broken
by Adrien Di Mascio 11 Jan '05

11 Jan '05

Hi all, I'm just beginning to play around with PyPy, and I got a traceback when trying to translate Python code to CL code. Here's the traceback : ######### >>> t = Translator(test.if_then_else) >>> t.cl() Traceback (most recent call last): File "<stdin>", line 1, in ? File "translator.py", line 165, in cl return self.generatecode(GenCL, input_arg_types, func) File "translator.py", line 184, in generatecode self.entrypoint, ann)] File "translator.py", line 205, in generatecode1 return g.emitcode(public) TypeError: emitcode() takes exactly 1 argument (2 given) >>> ######### A quick and dirty (partial) fix could be to add a "public=True" argument to the GenCL.emitcode() method, but I'm just a PyPy newbie for now, I don't really know how everything works and I'm not a Lisp Expert, so ... I just raise up the error here :-) Cheers, Adrien.

2 1

Re: [pypy-svn] r8201 - pypy/trunk/src/pypy/appspace
by Christian Tismer 11 Jan '05

11 Jan '05

ale(a)codespeak.net wrote: > Author: ale > Date: Tue Jan 11 08:58:40 2005 > New Revision: 8201 > > Added: > pypy/trunk/src/pypy/appspace/struct.py > Log: > Added the start of a struct module. It is not quite finished yet. > > The structure of the code is basically as in structmodule.c. > But some python goodies has been used - if that makes the > module less RPython I don't know. No, I think this is absolutely fine. I could translate it to RPython, and it works. See attached module. (The implementation will improve, but this is at least a proof that you wrote RPython) ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/

2 3

Re: [pypy-svn] r8201 - pypy/trunk/src/pypy/appspace
by Christian Tismer 11 Jan '05

11 Jan '05

ale(a)codespeak.net wrote: > Author: ale > Date: Tue Jan 11 08:58:40 2005 > New Revision: 8201 > > Added: > pypy/trunk/src/pypy/appspace/struct.py > Log: > Added the start of a struct module. It is not quite finished yet. > > The structure of the code is basically as in structmodule.c. > But some python goodies has been used - if that makes the > module less RPython I don't know. No, I think this is absolutely fine. I could translate it to RPython, and it works. See attached module. (The implementation will improve, but this is at least a proof that you wrote RPython) ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/

1 0

flow space and UnboundLocalError! Eek!
by Christian Tismer 11 Jan '05

11 Jan '05

Hi friends, I was playing with generated RPy functions, and just for fun, I ran my generator over its output. That should give an RPython interpreter for the whole pypy implementation. Not too useful, but nice to look at, better than disassembly :-) Here *the problem*: When I run flow space over my attached generated function, it crashes with an UnboundLocalError: w_26. This *is not* an error, because all the paths can only be walked in the order enforced by the big goto loop. But the flow space seems to step into a problem here. Well, flow space tries every branch, and most probably without looking at the data. Question: Is it possible to change the flow space to just ignore unbound variables? Or is this kind of code to be defined as NOT_RPYTHON ? The latter would be very bad, since I'm trying to create RPython, so it should be. An ugly solution would be to initialize all variables to some default. Please let me know ASAP -- ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/ #!/bin/env python # -*- coding: LATIN-1 -*- ##SECTION## ## filename 'genrpy.py' ## function 'ff' ## firstlineno 1062 ##SECTION## # global declarations # global object gcls_SystemError # global object gi_42 def f_ff(space, *args_w): kwlist = ["a", "b", "c"] w_1 = space.newtuple(list(args_w[3:])) _args_w = args_w[:3] defaults_w = (gi_3,) # XXX should parse args here, but no keyword support in gateway funcname = "ff" w_2, w_4, w_6 = PyArg_ParseMini(space, funcname, 2, 3, _args_w, defaults_w) return fastf_ff(space, w_2, w_4, w_6, w_1) def fastf_ff(space, w_2, w_4, w_6, w_1): goto = 1 # startblock while True: if goto == 1: v0 = space.is_true(w_1) if v0 == True: w_3, w_5, w_7, w_8 = w_2, w_4, w_6, w_1 goto = 3 else: assert v0 == False w_9, w_10, w_11, w_12 = w_2, w_4, w_6, w_1 goto = 2 if goto == 2: w_13 = space.add(w_9, w_10) v14 = space.is_true(w_12) if v14 == True: (w_15, w_16, w_17, w_18, w_19, w_20) = (w_9, w_10, w_11, w_12, w_13, v14) goto = 5 else: assert v14 == False w_21 = w_13 goto = 6 if goto == 3: v22 = space.is_true(w_8) if v22 == True: w_23, w_24, w_25, w_26, w_27 = w_3, w_5, w_7, w_8, v22 goto = 4 else: assert v22 == False w_28, w_29 = gcls_SystemError, gi_42 goto = 7 if goto == 4: w_30 = space.len(w_26) w_31 = space.newtuple([w_30, w_25]) w_21 = w_31 goto = 6 if goto == 5: w_32 = space.len(w_18) w_33 = space.newtuple([w_32, w_17]) w_21 = w_33 goto = 6 if goto == 6: return w_21 if goto == 7: raise OperationError(w_28, w_29) ##SECTION## ## filename 'genrpy.py' ## function '<lambda>' ## firstlineno 1142 ##SECTION## # global declarations # global object gfunc__lambda_ # global object gfunc_ff # global object gi_2 # global object gi_3 # global object gi_5 def f__lambda_(space, *args_w): kwlist = [] _args_w = args_w defaults_w = () # XXX should parse args here, but no keyword support in gateway funcname = "<lambda>" PyArg_ParseMini(space, funcname, 0, 0, _args_w, defaults_w) return fastf__lambda_(space, ) def fastf__lambda_(space, ): goto = 1 # startblock while True: if goto == 1: _tup = space.newtuple([gi_2, gi_3, gi_5]) w_0 = space.call(gfunc_ff, _tup) w_1 = w_0 goto = 2 if goto == 2: return w_1 ##SECTION## #************************************************************* def init_lambda__1(space): """NOT_RPYTHON""" class m: pass # fake module m.__dict__ = globals() from pypy.interpreter.gateway import interp2app m.gfunc__lambda_ = space.wrap(interp2app(f__lambda_)) m.gfunc_ff = space.wrap(interp2app(f_ff)) m.gi_2 = space.newint(2) m.gi_3 = space.newint(3) m.gi_5 = space.newint(5) from pypy.translator.genrpy import PyArg_ParseMini m.PyArg_ParseMini = PyArg_ParseMini from pypy.interpreter.error import OperationError m.OperationError = OperationError m.gcls_SystemError = space.wrap(SystemError) m.gi_42 = space.newint(42) # entry point: _lambda_, gfunc__lambda_) if __name__ == "__main__": from pypy.objspace.std import StdObjSpace space = StdObjSpace() init_lambda__1(space) print space.unwrap(space.call( gfunc__lambda_, space.newtuple([])))

1 0

tests porting status
by Samuele Pedroni 10 Jan '05

10 Jan '05

All tests apart appspace tests and some tests in tool/test are ported to py.test. The tool/test are easy to address. Given that appspace tests are currently run through CPython I wonder whether it would make sense to merge the branch, porting the few tests that were added to the head after the branch creation and think how to address exactly the appspace tests issue after that directly on the head. This would allow whatever work is going to happen on the head between now and the sprint to use py.test tests. Samuele.

2 1

Re: [pypy-dev] Upcoming PyPy sprint
by Armin Rigo 10 Jan '05

10 Jan '05

Hi Jacek, On Thu, Jan 06, 2005 at 07:41:08PM +0100, Jacek Generowicz wrote: > I would like to come, but the timing is rather unfortunate and it looks > like I would not be able to attend the whole event. However, I would be > able to commute (from Geneva) on a few of the days. > > Would I be able to pick up some knowledge of PyPy by attending a few > days, or would it be a complete waste of everybody's time? Would you be able to attend the beginning of the sprint? I fear that near the end we might all be in "quickly-hack-a-bit-more-we-want-this-to-work" mode... but the beginning should definitely be interesting, and you are most welcome! Armin

3 4

Re: [pypy-svn] r8078 - pypy/trunk/src/pypy/interpreter
by hpk＠trillke.net 10 Jan '05

10 Jan '05

On Wed, Jan 05, 2005 at 17:35 +0100, tismer(a)codespeak.net wrote: > Author: tismer > Date: Wed Jan 5 17:35:47 2005 > New Revision: 8078 > > Modified: > pypy/trunk/src/pypy/interpreter/pyopcode.py > Log: > changed LOAD_GLOBAL to support the flow space better. > In case of a NameError, where the space does not define NameError, > we raise a real NameError with a message. > > Modified: pypy/trunk/src/pypy/interpreter/pyopcode.py > ============================================================================== > --- pypy/trunk/src/pypy/interpreter/pyopcode.py (original) > +++ pypy/trunk/src/pypy/interpreter/pyopcode.py Wed Jan 5 17:35:47 2005 > @@ -525,8 +525,13 @@ > if not e.match(f.space, f.space.w_KeyError): > raise > message = "global name '%s' is not defined" % varname > - w_exc_type = f.space.w_NameError > - w_exc_value = f.space.wrap(message) > + try: > + w_exc_type = f.space.w_NameError > + w_exc_value = f.space.wrap(message) > + except AttributeError: > + # object space does not support it, so crash really > + raise NameError, (message + > + ", but %s has no NameError!" % f.space) > raise OperationError(w_exc_type, w_exc_value) > f.valuestack.push(w_value) I don't understand this change. Why is raising a NameError for not finding space.w_NameError better than just an AttributeError? This seems to me like mixing different levels (application level and interpreter level). It seems the flow object space could easily provide its own w_NameError and then you can check the usual way, catching an OperationError and then for e.match(space, space.w_NameError) without changing the interpreter. cheers (and happy new year to you, christian!), holger

4 5

Re: [pypy-dev] Upcoming PyPy sprint
by Armin Rigo 07 Jan '05

07 Jan '05

Hi, On Fri, Jan 07, 2005 at 12:54:04PM +0100, Adrien Di Mascio wrote: > Ludovic and I won't be able to be there before the 24th. Is it be > possible for you (Pypy team) to keep some of the "Introducing PyPy" > part for Monday and Tuesday ? Yes, I guess so. Armin

1 0

Running Python in reverse
by Alexander Schliep 07 Jan '05

07 Jan '05

Hi everyone, Christian Tismer encouraged me to post the following directly to the pypy mailing list. My main Python project is Gato, a software for visualizing (or animating) graph algorithms; see http://gato.sourceforge.net/wiki/pmwiki.php/Main/Screenshots. The main ingredients of Gato are a debugger subclass, some GUI elements and code for drawing graphs. The goal is to have an interactive, dynamic version of the classical comp.sci. text book, where, typically, some graph algorithm is given as pseudo code and you see (at best) a before, during, and after snapshot picture of its working on some graph. Python is a perfectly fine replacement for pseudo code and the execution and directly coupled visualization, which you can control just like a debugger, convey much more than static pictures. Winfried Hochstaettler, some university colleagues, and myself have used this for teaching discrete math, combinatorial optimization and comp.sci.classes with quite favorable comments from everyone involved. The number one request was always the ability to track back. I started to implement an instant replay of the last visualization effect (change of color, blink etc.) and started to think about a proper way of supporting the ability to step back in time. This essentially boils down to implementing one of the classical design patterns for supporting unlimited undo (and redo), treating the visualization effects as commands. This decouples the state (values of all variables used) of the algorithm from the state of the visualization, hence running the algorithm after a couple of Undos is not possible (One could fake that by Redoing everything and then continuing execution). Supporting an update of all variables gets kind of messy in standard Python. A cleaner approach would be to have a Python interpreter which can run backwards. Christian thinks it would be feasible in PyPy. This actually would be extremely nice for a number of applications - teaching Python - teaching algorithms with Python - debugging in general I am somewhat embarrassed to ask for a feature without much to offer. But realistically, I cannot promise more than to be a tester and happy user. Best, Alexander PS: Gato is LGPL. The algorithms we have are copyright Springer, as we have a textbook & software package coming out this year. PPS: There is a C-syntax-based tool which can run backwards: http://www.dis.uniroma1.it/~demetres/Leonardo/Leonardo.html -- schliep(a)molgen.mpg.de http://algorithmics.molgen.mpg.de

2 1