PyPy Warsaw Sprint (October 21-25th, 2014)

Hi all, Here's the announcement (below) for the next PyPy sprint, in one month's time in Warsaw. It will take place just after the Polish PyCon Pl'14 conference, which is also in Poland, although not in Warsaw. See http://pl.pycon.org/2014/en/ in case you're interested. (There is of course no need to attend one in order to attend the other.) Armin ===================================================================== PyPy Warsaw Sprint (October 21-25th, 2014) ===================================================================== The next PyPy sprint will be in Warsaw, Poland for the first time. This is a fully public sprint. PyPy sprints are a very good way to get into PyPy development and no prior PyPy knowledge is necessary. ------------------------------ Goals and topics of the sprint ------------------------------ For newcomers: * Bring your application or library and we'll help you port it to PyPy (if needed), benchmark and profile. * The easiest way to start hacking on PyPy is to write support for some missing Python 3.3 functionality, or to work on numpy. We'll also work on more specific topics, depending on who is here and what their interest is, like some missing GC/JIT optimizations, software transactional memory, etc. ----------- Exact times ----------- The work days should be October 21st - 25th, 2014. There might be a day or an afternoon of break in the middle. We'll typically start at 10:00 in the morning. ------------ Location ------------ The sprint will happen within a room of Warsaw University. The address is Pasteura 5 (which is a form of "Pasteur street"), dept. of Physics, room 450. The person of contact is Maciej Fijalkowski. -------------- Registration -------------- If you want to attend, please register by adding yourself to the "people.txt" file in Mercurial:: https://bitbucket.org/pypy/extradoc/ https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/warsaw-2014 or on the pypy-dev mailing list if you do not yet have check-in rights:: http://mail.python.org/mailman/listinfo/pypy-dev Remember that Poland is a regular Schengen zone EU country, with main-EU-zone power adapters.

Hi! My name is Kostia Lopuhin, and I would like to come to the sprint. If all goes well, I will be at the sprint 21-24th and a part of 25th. I would like to work on JIT optimizations, I am particularly interested in improving short loops, but understanding that this is a complex topic, I just want to start with something :) Also maybe I can work on using to use CPython modules from PyPy, using this http://morepypy.blogspot.ru/2011/12/plotting-using-matplotlib-from-pypy.html embedding trick by Maciej Fijalkowski, I extended it a little here https://bitbucket.org/kostialopuhin/embed-cpython 2014-09-23 10:22 GMT+04:00 Armin Rigo <arigo@tunes.org>:
Hi all,
Here's the announcement (below) for the next PyPy sprint, in one month's time in Warsaw. It will take place just after the Polish PyCon Pl'14 conference, which is also in Poland, although not in Warsaw. See http://pl.pycon.org/2014/en/ in case you're interested. (There is of course no need to attend one in order to attend the other.)
Armin
===================================================================== PyPy Warsaw Sprint (October 21-25th, 2014) =====================================================================
The next PyPy sprint will be in Warsaw, Poland for the first time. This is a fully public sprint. PyPy sprints are a very good way to get into PyPy development and no prior PyPy knowledge is necessary.
------------------------------ Goals and topics of the sprint ------------------------------
For newcomers:
* Bring your application or library and we'll help you port it to PyPy (if needed), benchmark and profile.
* The easiest way to start hacking on PyPy is to write support for some missing Python 3.3 functionality, or to work on numpy.
We'll also work on more specific topics, depending on who is here and what their interest is, like some missing GC/JIT optimizations, software transactional memory, etc.
----------- Exact times -----------
The work days should be October 21st - 25th, 2014. There might be a day or an afternoon of break in the middle. We'll typically start at 10:00 in the morning.
------------ Location ------------
The sprint will happen within a room of Warsaw University. The address is Pasteura 5 (which is a form of "Pasteur street"), dept. of Physics, room 450. The person of contact is Maciej Fijalkowski.
-------------- Registration --------------
If you want to attend, please register by adding yourself to the "people.txt" file in Mercurial::
https://bitbucket.org/pypy/extradoc/ https://bitbucket.org/pypy/extradoc/raw/extradoc/sprintinfo/warsaw-2014
or on the pypy-dev mailing list if you do not yet have check-in rights::
http://mail.python.org/mailman/listinfo/pypy-dev
Remember that Poland is a regular Schengen zone EU country, with main-EU-zone power adapters. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev

Hi Kostia, On 27 September 2014 21:09, Костя Лопухин <kostia.lopuhin@gmail.com> wrote:
My name is Kostia Lopuhin, and I would like to come to the sprint.
Welcome :-)
I would like to work on JIT optimizations, I am particularly interested in improving short loops, but understanding that this is a complex topic, I just want to start with something :) Also maybe I can work on using to use CPython modules from PyPy, using this http://morepypy.blogspot.ru/2011/12/plotting-using-matplotlib-from-pypy.html embedding trick by Maciej Fijalkowski, I extended it a little here https://bitbucket.org/kostialopuhin/embed-cpython
Both are possible to do, yes. Arguably, the most important improvement in the JIT is to bring down the warm-up time, but that is not a big issue for short loops. They would however benefit from the second-best improvement: better assembler generation. A bientôt, Armin.
participants (2)
-
Armin Rigo
-
Костя Лопухин