[pypy-dev] Please submit status reports

Rocco Moretti roccomoretti at netscape.net
Sun May 25 21:24:08 CEST 2003

Jacob Hallén <jacob at strakt.com> wrote:

>To help the sprinters, we would be grateful if everyone could post a brief
>status report about the latest things you did on the project and what you
>think the next step in this area is. I particular, we would be grateful if
>Rocco, Dinu, Holger and all the sprinters would provide input.


  Most of my time on PyPy since the last sprint was involved in setting up 
a testing framework I felt comfortable using (submitted as PyPyTest.py in 
subversion under /user/rocco/tool/). To get the CPython regression tests 
to work properly, I had to improve exception matching. Once that was 
working, the missing exec statement functionality was low hanging fruit. 
Aside from my recent philosophy posts, I haven't done anything more with 
PyPy due to time constraints.

Where to next:

  I'm of the opinion that the acid test for this phase of PyPy development 
is the sucessful execution of the CPython regression tests - does PyPy do 
what CPython is supposed to do.  So squashing regression test bugs is high 
on my priority list. I think some of the bugs will need a slight core 
redesign in order to fix. So I'd think about the cause of the regression 
test bugs, and how to redesign the core to fix them.

  Once that's done, the StdObjSpace needs completion and testing, and if 
there is time left, adapting/creating an Application Level parser/compiler.
And unless I miss my guess, that'll take us to the proposed 0.1.0 
milestone, at which point the fun can begin.

In short, empty the issues board. (Assuming "Finish StdObjSpace" and "No 
PyPy Compiler" get added at some point.)


McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!

Get AOL Instant Messenger 5.1 free of charge.  Download Now!

More information about the Pypy-dev mailing list