Mailman 3 March 2003 - pypy-dev

Feature Request: Use valid python ;-)
by logistix March 7, 2003

March 7, 2003

I was processing my pythonpath with parser and it blew up on several pypy files. Here are the details, but I can provide a diff if necessary (and would have if I knew where to): longobject.py - mixes tabs and spaces listobject.py: class W_ListObject: ... should be class W_ListObject:pass iterobject.py is invalid longobject.py should be. def long_getattr(i, attr): if attr == "__class__": return int raise AttributeError#, ....

2 2

I'm off for wa while...
by Christian Tismer March 7, 2003

March 7, 2003

Hi friends, sorry to tell you so, but I will be away from this project for a while. I'm in trouble with my parent's health, I haven't done my sponsored Stackless work for months and they are about to cancel my contracts, and currently I'm driving myself into a deadlock: I am unable to concentrate on anything. For that reason, I'm drawing a hard decision: I will not work on PyPy until Stackless 3.0 is out. I will cancel my PyCon talk, which is very hard for me. Most probably, I will be back,… [View More]

1 0

RE: [pypy-dev] Why is there a separate ExecutionContext?
by roccomoretti＠netscape.net March 6, 2003

March 6, 2003

"logistix" <vze55z8s(a)verizon.net> wrote: >Would it be semantically clearer if PyFrames got an executioncontext >object in the constructor instead of the space object? Space could >still be accessed via frame.ec.space. Frame.space.getexecutioncontext() >seems like you're running in circles. Actually, in the interest of generality, I'd argue that ExecutionContexts should not contain a link to the object space - it should be a per frame value. If you think of a … [View More]

3 2

Why is there a separate ExecutionContext?
by logistix March 5, 2003

March 5, 2003

Okay, Here's a summary of what I'm seeing: An ExecutionContext object is created. This is a stack of frames. A PyFrame is created. This has no knowledge of frames above it on the stack. The ExecutionContext accepts the PyFrame for evaluation, and calls the PyFrame's eval passing itself in as a parameter. The PyFrame's eval method just treats the ExecutionContext as a local var, it isn't stored in the class. PyFrame calls appropriate bytecode implementation functions, passing itself as a … [View More]

3 4

Code review possible?
by Christian Tismer March 4, 2003

March 4, 2003

Howdy, as people have seen me struggling quite much to find out how we should do what which way, with not so much success, I came up with Yet Another Fine Idea(TM): Wouldn't it be the right time to do a code review on the C sources? All of them? I'm thinking of some summary about every C module that I know well (these are many). This would be a listing of functions, what they do, their scope, what the external references are, and how I think this might be rewritten in Python. Having a bigger … [View More]

4 5

Pypy frontend/ testall.py
by logistix March 3, 2003

March 3, 2003

I've written a small script that'll allow you to run .py scripts via pypy. Ultimately, it'll incorporate all of the functionality of calling 'python' from the command-line. Normally, I'd get some more work done before distributing it, but it is enough to run testall.py in the test directory, so I thought it might be of interest. It should be noted that testall.py fails quite spectacularly, as can be expected at this point, and aborts execution. I piped the results to a logfile, but there … [View More]

4 7

hash negotiation
by Christian Tismer March 3, 2003

March 3, 2003

Hi, additional to an integer change, I also saw a change of the hash implementation: def int_hash(space, w_int1): #/* XXX If this is changed, you also need to change the way # Python's long, float and complex types are hashed. */ ## x = w_int1.intval ## if x == -1: ## x = -2 ## return W_IntObject(x) # XXX unlike CPython we have no need to special-case the value -1 return w_int1 I intentionally repeated CPython's implementation, which special cases -1 as … [View More]

2 3

Fork lib and pythonpath?
by logistix March 3, 2003

March 3, 2003

First off, apologies if this shows up as a dupe post. I posted via gmane.org about 6 hours ago and it never showed up. This brief interactive session scares me a little. ---START CONSOLE TEXT--- Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\grant>cd \python22\lib\site-packages\pypy\interpreter C:\Python22\Lib\site-packages\pypy\interpreter>python interactive.py Python 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] … [View More]

3 2

interface changes (would-have-been: builtin -- getting started)
by Christian Tismer March 3, 2003

March 3, 2003

Hi friends, as stated in my last message, I think that we suffer from a lack of "recipies" how to get started, and we are all eager to do some implementation. I'd like to encourage everybody on this list to do get started, although we are probably defining interfaces "after the fact". That menas, you may write something up, but you will need to be aware that the interface might be changed. This is not as bad as it sounds, it just means that you shouldn't worry about the interfaces too much, … [View More]instead concentrate on the meat of the implementation. Just to give you an example, I just discovered that "my" integer object happened to change without notice. On Armin's request, I dropped the "cmp" operator and implemented rich comparisons. Suddenly, I today see my if-then-else battery changed into six single functions. This is fine with me, although I had appreciated some notice about that change, either by private emails or by an automagic update magic from Subversion -- anyway, this doesn't matter so much. What does matter a bit is that we don't have a general policy about interfaces, and that these appear to be changed from time to time, without notice. I think it would be nice not to change such things without notice, but to post a request for interface change to the PyPy list, and maybe doing the change after some confirmation. Essentially, this project is not owned by a few people, but this is a community effort. If this is not going to be a basic principle, I'd like to know, and to be able to decide on myself, if I want to continue to contribute. Open source is a nice thing, but I do think that there should be some "netiquette" about changing "anyone's code". At least, a notice of change is required. I don't believe that we should adopt a concept of "godfathers" who are allowed to mess with everything without at least owing the authors some measures of a note! Actually, I wanted to give some hints about contributing to builtins, but unfortunately that change distracted me from the point, so I'm going to write yet another posting, to get at the point. cheers - chris -- Christian Tismer :^) <mailto:tismer@tismer.com> Mission Impossible 5oftware : 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 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/ [View Less]

5 6

Re: hints about contributing to builtins
by Christian Tismer March 3, 2003

March 3, 2003

Laura Creighton wrote: > I would like some :-) Well, it's really hard to give advice. I have my opinions, which you know are sometimes quite different from other's, and the list seems to be quite quiet on the weekend... There are a couple of open issues when looking into builtins. One of these is btw., that we didn't define a module object, yet, which we really need since builtins is a module. Then, by looking at some simple function in builtinmodule, even more questions are raised: … [View More]static PyObject * builtin_isinstance(PyObject *self, PyObject *args) { PyObject *inst; PyObject *cls; int retval; if (!PyArg_ParseTuple(args, "OO:isinstance", &inst, &cls)) return NULL; retval = PyObject_IsInstance(inst, cls); if (retval < 0) return NULL; return PyInt_FromLong(retval); } What do we have here? First of all, there is the Python calling convention, that every function call has a self argument, may this be used or not. Builtins doesn't use it at all, so you always can ignore self. But then, what about the arg tuple? I didn't find any definition how this is handled. Well, let me look into the interpreter, there they must have some notation of a function call.............. ...back from there. As far as I can see it, we end up being called like this: w_result = f.space.call(w_function, w_arguments, w_keywords) f.valuestack.push(w_result) (from opcode.py) Now let me dive into objectspace :-) Unfortunately, even the trivial space doesn't run under PythonWin or Boa constructor, so I can't use the debugger. Aha, as it looks right now, we do not distinguish different calling conventions, and we have to deal with something like def builtin_isinstance(*args, **kwds): The problem is then that we don't have PyArg_ParseTuple and friends, yet, and we have not settled down where we can find PyObject_IsInstance implemented. Question: To get things going, should we simply use the given function interfaces from CPython, and code some PyArg_ParseTuple away? Question: Where do we put undefined stuff, when we want to write a module like builtins? Sigh... This seems to be a bit too hard for me, tonight. Maybe someone on the list has an idea how to bootstrap all this stuff? good nite - chris -- Christian Tismer :^) <mailto:tismer@tismer.com> Mission Impossible 5oftware : 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 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/ [View Less]

2 1