Mailman 3 June 2007 - pypy-dev

Re: [pypy-dev] [LLVMdev] Vilnius/Post EuroPython PyPy Sprint 12-14th of July
by Armin Rigo June 23, 2007

June 23, 2007

Hi Anton, (CC'ing to pypy-dev) On Fri, Jun 22, 2007 at 09:59:12PM +0400, Anton Korobeynikov wrote: > > - support for LLVM 2.0 for the llvm backend > Is there any detailed information, how the sprint will touch this topic? I don't have many details, but there are three subtasks regarding LLVM: on the one hand, we did a small addition to the translation toolchain that is not yet supported by our backend generating LLVM code, so the first subtask is this "maintenance" task, which … [View More]

2 1

About adding a blist implementation...
by Elmo Mäntynen June 22, 2007

June 22, 2007

Fijal mentioned blist on irc and I got interested and read about it. This really seems the kind of thing I might even accomplish in a reasonable time, so if no one hasn't started on it, I'd like to try. I'm somewhat familiar with the multilist interface (seems very clear), so the challenge for me would be the [efficient] algorithmic and rpythonic coding style, the algorithm itself, and teaching myself all of that. It is very much possible that I will again abandon this as I have done with some … [View More]

3 4

Vilnius/Post EuroPython PyPy Sprint 12-14th of July
by Armin Rigo June 22, 2007

June 22, 2007

======================================================== Vilnius/Post EuroPython PyPy Sprint 12-14th of July ======================================================== The PyPy team is sprinting at EuroPython again and we invite you to participate in our 3 day long sprint at the conference hotel - Reval Hotel Lietuva. If you plan to attend the sprint we recommend you to listen to the PyPy technical talks (`EuroPython schedule`_) during the conference since it will give you a good overview of … [View More]the status of development. On the morning of the first sprint day (12th) we will also have a tutorial session for those new to PyPy development. As 3 days is relatively short for a PyPy sprint we suggest to travel back home on the 15th if possible (but it is ok to attend less than 3 days too). ------------------------------ Goals and topics of the sprint ------------------------------ There are many possible and interesting sprint topics to work on - here we list some possible task areas: * completing the missing python 2.5 features and support * write or port more extension modules (e.g. zlib is missing) * identify slow areas of PyPy through benchmarking and work on improvements, possibly moving app-level parts of the Python interpreter to interp-level if useful. * there are some parts of PyPy in need of refactoring, we may spend some time on those, for example: - rctypes and the extension compiler need some rethinking - support for LLVM 2.0 for the llvm backend - ... * some JIT improvement work * port the stackless transform to ootypesystem * other interesting stuff that you would like to work on ...;-) ------------ Registration ------------ If you'd like to come, please subscribe to the `pypy-sprint mailing list`_ and drop a note about your interests and post any questions. More organisational information will be sent to that list. Please register by adding yourself on the following list (via svn): http://codespeak.net/svn/pypy/extradoc/sprintinfo/post-ep2007/people.txt or on the pypy-sprint mailing list if you do not yet have check-in rights: http://codespeak.net/mailman/listinfo/pypy-sprint --------------------------------------- Preparation (if you feel it is needed): --------------------------------------- * read the `getting-started`_ pages on http://codespeak.net/pypy * for inspiration, overview and technical status you are welcome to read `the technical reports available and other relevant documentation`_ * please direct any technical and/or development oriented questions to pypy-dev at codespeak.net and any sprint organizing/logistical questions to pypy-sprint at codespeak.net * if you need information about the conference, potential hotels, directions etc we recommend to look at http://www.europython.org. We are looking forward to meet you at the Vilnius Post EuroPython PyPy sprint! The PyPy team .. See also .. .. _getting-started: http://codespeak.net/pypy/dist/pypy/doc/getting-started.html .. _`pypy-sprint mailing list`: http://codespeak.net/mailman/listinfo/pypy-sprint .. _`the technical reports available and other relevant documentation`: http://codespeak.net/pypy/dist/pypy/doc/index.html .. _`EuroPython schedule`: http://indico.cern.ch/conferenceTimeTable.py?confId=13919&showDate=all&show… [View Less]

1 0

Scheme interpreter - evaluation context
by Jakub Gustak June 22, 2007

June 22, 2007

I was looking into some code, JS interpreter to be exact. I wonder what are the pros and cons of implementing evaluation context as stack/list (as in JS interpreter) in opposite to implementing it as dictionary. If there is one name space for all objects in Scheme (I mean, there is no distinction between variable or function when naming them), dictionary would be the most straight forward. There is no need for a special way to resolve naming conflicts and so on. Or am I missing something? Cheers, Jakub Gustak

2 1

Re: [pypy-dev] lltypesystem typecache
by Amaury Forgeot d'Arc June 21, 2007

June 21, 2007

Scott Dial wrote: > Greetings, > > The typecache in subversion repository is missing the 32bit windows > platform that I am running the windows tests against, and on occasion > (like today) I noticed it caused a update conflict due to Armin's > changes in r44398. If someone could add this one, thanks. > > -Scott I have seen the same behaviour, and my diffs are the same. I just commited them. -- Amaury Forgeot d'Arc

1 0

PyPy sync next week?
by Maciek Fijalkowski June 16, 2007

June 16, 2007

I know you're quite tired right now and all, but I think it would be good to make some kind of pypy-sync next week or even the week after (we need to decide on sprint topics anyway). Particularly I would like to know people's opinion on pypy's scope. What we would like to support, what we would like to drop support for, what are the short-term project directions etc. What do you think? Cheers, fijal

6 8

Re: [pypy-dev] Work plan for PyPy
by Laura Creighton June 15, 2007

June 15, 2007

In a message of Fri, 15 Jun 2007 01:01:17 +0200, Antonio Cuni writes: <snip> > >Finally, a note which is not related with the work plan but to a >question that appeared in the logs; someone asked whether we want to >"sell" RPython as a stand-alone product. >Last sunday I gave a PyPy talk at Pycon italy and, surprisingly enough, >RPython was perceived as the only (or the most relevant) usable product >of the pypy project. I tried hardly to explain that rpython is … [View More]

2 1

Pygame viewer
by Armin Rigo June 15, 2007

June 15, 2007

Hi all, I've refactored a bit the Pygame viewer. Can people with OS/X or Windows give it a try? It is currently in the branch pypy/branch/graphserver-dist/. I'll merge it when I'm sure there are no platform issues. It is supposed to support the following features: * all pygame usage is done in a subprocess, which cannot take away the whole parent process if it segfaults. * regular usage should continue to work as before, e.g. t.view() in translatorshell.py, as well as the translate.… [View More]

1 0

Re: [pypy-dev] PyPy sync next week?
by Laura Creighton June 11, 2007

June 11, 2007

In a message of Mon, 11 Jun 2007 10:18:58 +0200, Antonio Cuni writes: >Maciek Fijalkowski wrote: > >> Ok, so what about usual Thursday 17:00? > >Fine for me. > >ciao Anto me too. Laura

1 0

play1.pypy.org not working
by Leonardo Santagada June 7, 2007

June 7, 2007

I tried it today and found a 502 proxy error. -- Leonardo Santagada "If it looks like a duck, and quacks like a duck, we have at least to consider the possibility that we have a small aquatic bird of the family anatidae on our hands." - Douglas Adams

1 0