Mailman 3 March 2005 - pypy-dev

code/dev status reports?
by hpk＠trillke.net 18 Mar '05

18 Mar '05

Hi pypythonistas, i think along with the releases we should think about improving the communication situation: we are mostly communicating over IRC, real-life sprints and pypy-svn which is quite effective but it makes it hard for people outside those loops to follow at all, i guess. Is there interest having some kind of a monthly status report about advances in the code base or other dev-related news? cheers, holger

8 7

Dynamic compilation via pyrex?
by Grant Olson 14 Mar '05

14 Mar '05

> We use Pyrex to statically compile dynamically generated > source code. The compiled code is then imported into the > process that generated the code. But surely, this still means > we are statically compiling things. Let me guess, this doesn't work on Windows yet? ;-) > Let me note that with 'dynamic' we usually mean even more dynamic > than your pyasm, in that you could assemble and run inline fragments > of machine code at runtime (for implementing e.g. Psyco in PyPy). There is an api in pyasm that you can use to do this. You don't need to just pass in a monolithic string like I did in the example. That was just easier for most people to understand. There is a little documentation on this and it will be expanded in the next release. I'm also toying with the notion of something similar to a main() function that gets executed automatically at runtime instead of forcing you to bind to function names and calling the functions. That is, unless you're talking about something like: def foo(a,b): print a + b MOV EBX, [EBP-4] print EBX That I can't do. I would obviously have to fork CPython to implement something like that, and that's not something I'm personally interested in. I'm not even sure if this would make sense in an optimized build. -Grant

3 2

Dynamic compilation via pyrex?
by Grant Olson 13 Mar '05

13 Mar '05

I'm working on a dynamic x86 assembler for python. Someone on comp.lang.python mentioned that you guys were dynamically compiling python code via pyrex. I was under the impression that this was static compilation. Which one of us is right? I tried digging around your website some, but couldn't find any info. BTW, the interpreter is in much better shape than when I last checked it out (probably 18 months ago ;-) ) -Grant

2 1

summaries on builtin types/modules
by Samuele Pedroni 11 Mar '05

11 Mar '05

Hi. I have played a bit with generating static html pages summarizing where we stand wrt the implementations of builtins. A first cut can be seen starting here: http://codespeak.net/~pedronis/deltareports/modules-index.html the numbers refer to totals, numbers/percent of missing for functions/attributes of modules and/or classes/types. Red/maroon means missing, incomplete. Faked stuff is considered missing. There are buttons to switch locally to different sort orders.

2 2

Re: [pypy-svn] r9590 - in pypy/dist/pypy: annotation annotation/test translator/test
by Michael Hudson 04 Mar '05

04 Mar '05

pedronis(a)codespeak.net writes: > Author: pedronis > Date: Wed Mar 2 19:40:07 2005 > New Revision: 9590 > > Modified: > pypy/dist/pypy/annotation/classdef.py > pypy/dist/pypy/annotation/model.py > pypy/dist/pypy/annotation/test/test_model.py > pypy/dist/pypy/annotation/unaryop.py > pypy/dist/pypy/translator/test/snippet.py > pypy/dist/pypy/translator/test/test_annrpython.py > Log: > don't bump classdef revision number if only a fresher revision in an > attribute is involved, notice that we still reflow even in this > case. > > contains logic modified to let caller distinguish this situation, > RevDiff (a false value) is returned if the only reason for a false > contains relationship is rev numbers. > > without these changes the new test analysing make_eo would recurse > infinititely. At some point, we're *really* going to want to document some of this stuff! I.e. something approaching a proof of correctness and termination for the annotator. I guess having a correct and/or terminating annotator would be a good start... Cheers, mwh -- <AdamV> SamB: PHP's basic control structure is the "database timeout error". -- from Twisted.Quotes

3 3