[pypy-dev] Upcoming Sprint

Niko Matsakis niko at alum.mit.edu
Tue Apr 7 14:19:53 CEST 2009


>> Due to the enormous time demands on my PhD, I've been out of touch   
>> lately!  I follow from the blog though :) and it seems like you  
>> guys  have been doing great work.
>
> When do you plan to finish the PhD?

That's always a difficult question to answer precisely... at this  
point I am hoping to finish in about a year, but time will tell.

>> I am hoping to attend the sprint in Leysin.  I would be able to  
>> come  from the 14th until the 19th (I have to be back on the 20th,  
>> so I  figure I'd leave 19th in the afternoon/evening).  I'd have no  
>> problem  sharing a room, though I'm not sure if the fact that I  
>> can't stay for  the full sprint would be an issue.
>
> I wouldn't mind sharing a room with you and having to pay more for  
> the remaining days (and having a bit of quiet), since the uni is  
> paying anyway. Could you add yourself to this file:

Great!

> http://codespeak.net/pypy/extradoc/sprintinfo/leysin-winter-2009/people.txt

Done!

>> As for something to work on: besides hacking on whatever you guys   
>> think is important, I was considering porting one of my thesis  
>> ideas  to Python.  It has to do with an alternate means of  
>> specifying  parallel programs (sort of a mix between threads and  
>> futures).  Right  now it exists in slightly different forms as both  
>> a Java and Python  library (sorry, no web page), but I thought that  
>> by integrating it  into the interpreter I might be able to do more,  
>> such as dynamic race  detection.  My concern is that because this  
>> is an experimental  research topic, it doesn't really help with the  
>> goal of preparing the  interpreter for general use.  If it's not an  
>> appropriate topic for the  sprint, then a compromise might be any  
>> tasks that would help me to  learn about the interpreter so I can  
>> see better how to add my changes.
>
> Yes, the general focus of the sprint is the release (and I am sure  
> there is work in that area that will help you learn about the  
> interpreter). However, I guess that some experimental work on the  
> side is fine, as long as it doesn't take up the full week.

Makes sense.


Niko



More information about the Pypy-dev mailing list