|
The next PyPy sprint will be in Leysin, Switzerland, for the thirteenth time. This is a fully public sprint: newcomers and topics other than those proposed below are welcome. (Note: this sprint is independent from the suggested April-May sprint in Poland.) Goals and topics of the sprintThe list of topics is open, but here is our current list: |
 |
- cffi tutorial/overview rewrite
- py3 test runners are too complicated
- make win32 builds green
- make packaging more like cpython/portable builds
- get CI builders for PyPy into mainstream projects (Numpy, Scipy, lxml, uwsgi)
- get more of scientific stack working (tensorflow?)
- cpyext performance improvements
- General 3.5 and 3.6 improvements
- JIT topics: guard-compatible, and the subsequent research project to save and reuse traces across processes
- finish unicode-utf8
- update www.pypy.org, speed.pypy.org (web devs needed)
As usual, the main side goal is to have fun in winter sports :-) We can take a day off (for ski or anything else).
Exact times
Work days: starting March 18th (~noon), ending March 24th (~noon).
Please see announcement.txt for more information.
Can we expect a python 3.6 support released anytime soon? Thanks!
ReplyDeleteIt would be nice to have tensorflow working on pypy, even if there aren't many real world cases where this is useful, as most tensorflow does not use python for much heavy lifting.
ReplyDeleteHi PyPy-team!
ReplyDeleteWhile I was checking out a reinforcement learning repo I thought it would benefit a lot from have the games it was learning in something faster that CPython. So I had another look at PyPy. Tensorflow I could not install so I am really happy that this is on the agenda for the next sprint!
good luck and have fun!
Eric