PyPy Development: Leysin Winter Sprint Summary

Why don't you join us next time?

1.  Planning Session: Tasks from previous days that have seen progress or are completed are noted in a shared document. Everyone adds new tasks and then assigns themselves to one or more tasks (usually in pairs). As soon as everybody is happy with their task and has a partner to work with, the planning session is concluded and the work can start.
2. Discussions: A sprint is a good occasion to discuss difficult and important topics in person. We usually sit down in a separate area in the sprint room and discuss until a) nobody wants to discuss anymore or b) we found a solution to the problem. The good thing is that usally the outcome is b).
3. Lunch: For lunch we prepare sandwiches and other finger food.
4. Continue working until dinner, which we eat at a random restaurant in Leysin.
5. Goto 1 the next day, if sprint has not ended.

Sprint Summary   

• Work towards releasing PyPy 3.5 (it will be released soon)
• CPython Extension (CPyExt) modules on PyPy
• Have fun in winter sports (a side goal)

Highlights

• We have spent lots of time debugging and fixing memory issues on CPyExt. In particular, we fixed a serious memory leak where taking a memoryview would prevent numpy arrays from ever being freed. More work is still required to ensure that our GC always releases arrays in a timely manner.
• Fruitful discussions and progress about how to flesh out some details about the unicode representation in PyPy. Our current goal is to use utf-8 as the unicode representation internally and have fast vectorized operations (indexing, check if valid, ...).
• PyPy will participate in GSoC 2017 and we will try to allocate more resources to that than last year.
• Profile and think about some details how to reduce the starting size of the interpreter. The starting point would be to look at the parser and reduce the amount of strings to keep alive.
• Found a topic for a student's master thesis: correctly freeing cpyext reference cycles.
• Run lots of Python3 code on top of PyPy3 and resolve issues we found along the way.
• Initial work on making RPython thread-safe without a GIL.

List of attendees