Diff for "PyPySprint"

Differences between revisions 9 and 28 (spanning 19 versions)

PyPy Sprint

In the four days from 19th March till 22th March (inclusive) the PyPy team will host a sprint on their new Python-in-Python implementation. The PyPy project was granted funding by the European Union as part of its Sixth Framework Program, and is now on track to produce a stackless Python-in-Python Just-in-Time Compiler by December 2006. Our Python implementation, released under the MIT/BSD license, already provides new levels of flexibility and extensibility at the core interpreter and object implementation level.

Armin Rigo and Holger Krekel will also give talks about PyPy and the separate py.test tool (used to perform various kinds of testing in PyPy) during the conference.

Naturally, we are eager to see how the other re-implementation of Python, namely IronPython, is doing and to explore collaboration possibilities. Of course, that will depend on the degree of openness that Microsoft wants to employ.

The Pycon2005 sprint is going to focus on reaching compatibility with CPython (currently we target version 2.3.4) for our PyPy version running on top of CPython. One goal of the sprint is to pass 60% or more of the unmodified regression tests of mainline CPython. It will thus be a great way to get to know CPython and PyPy better at the same time! Other possible work areas include:

translation to C to get a first working lower-level representation of the interpreter "specified in Python"
integrating and implementing a full parser/compiler chain written in Python perhaps already targetting the new AST-branch of mainline CPython
fixing various remaining issues that will come up while trying to reach the compatibility goal
integrating or coding pure python implementations of some Python modules which are currently written in C.
whatever issues you come up with! (but please tell us before hand so we can better plan introductions etc.)

If you have other interests feel free to suggest different sprint topics! Besides core developers Bea Düring, our "process manager" will be working off location (IRC/email) during the sprint to help improving and document our sprint and agile development process.

We are going to give tutorials about PyPy's basic concepts and provide help to newcomers usually by pairing them with experienced pypythonistas. However, we kindly ask newcomers to be present on the first day's morning (19th of March) of the sprint to be able to give everyone a smooth start into the sprint. So far most newcomers have had few problems in getting a good start into our codebase. However, it is good to have the following preparational points in mind:

experience programming in the Python language and interest to dive deeper
subscription to pypy-dev and pypy-sprint.
have a subversion-client, Pygame and graphviz installed on the machine you bring to the sprint.
have a look at our current documentation, especially the architecture and getting-started documents.

The pypy-dev and pypy-sprint lists are also the contact points for raising questions and suggesting and discussing sprint topics beforehand. We are also on #pypy on freenode most of the time. Please don't hesitate to contact us or introduce yourself, your background and your interests!

Logistics

Organizational details will be posted to pypy-sprint and are or will be available in the Pycon2005-Sprint wiki here:

http://www.python.org/moin/PyConDC2005/Sprints

Registration

send mail to pypy-sprint@codespeak.net, stating the days you can be present and any specific interests if applicable.

Registered Participants

If you aren't planning to be available for all four days of the sprints, please note which days you will be around.

Jacob Hallén (Virginian Suites, near Rosslyn)
Armin Rigo
Samuele Pedroni (Virginian Suites, near Rosslyn)
Anders Chrigström (Virginian Suites, near Rosslyn)
Christian Tismer (Key Bridge, shares with Lutz))
Richard Emslie (Econo Lodge Metro, shares with Holger)
Holger Krekel (Econo Lodge Metro, shares with Richard)
Lutz Pälike (Key Bridge, shares with Christian)
Bob Ippolito
Jonathan Riehl
Alan Mcintyre (Washington Terrace Hotel)

CategoryPyCon2005

Page

User

PyPy Sprint

Logistics

Registration

Registered Participants

-  ⇤ ← Revision 9 as of 2005-02-02 16:49:07 → 
  Size: 3879
  Editor: enzo
  Comment:
+   ← Revision 28 as of 2008-11-15 13:59:39 → ⇥
  Size: 4619
  Editor: localhost
  Comment: converted to 1.6 markup
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-In the four days before the conference the [http://codespeak.net/pypy PyPy] team hosts a sprint on their new Python-in-Python implementation. Until December 2006 the project aims to produce an MIT/BSD-licensed stackless version of Python with a JIT-compiler and new levels of flexibility and extensibility at the core interpreter and object implementation level.  Recently the project was granted EU-funding for their research and implementation plans. Armin Rigo and Holger Krekel will also give talks about PyPy and the separate [http://codespeak.net/py/current/doc/test.html py.test] tool (used to perform the various kinds of testing in PyPy) during the conference.
+== PyPy Sprint ==
 Line 3:
-The sprint is going to focus on reaching compatibility with CPython (currently we target version 2.3.4) for our PyPy version running on top of CPython.  One goal of the sprint is to pass 60% of the unmodified regression tests of mainline CPython. (We may modify that number depending on our progress before the sprint :-). It will thus be a great way to get to know CPython and PyPy better at the same time! Other possible work areas include:
+In the four days from 19th March till 22th March (inclusive)
the PyPy team will host a sprint on their new Python-in-Python
implementation.   The PyPy project was granted funding by the
European Union as part of its Sixth Framework Program,
and is now on track to produce a stackless Python-in-Python
Just-in-Time Compiler by December 2006.  Our Python
implementation, released under the MIT/BSD license, already
provides new levels of flexibility and extensibility at the
core interpreter and object implementation level.
-Line 5:
+Line 13:
- * translation to C to get a first working lower-level representation of the interpreter
+Armin Rigo and Holger Krekel will also give talks about PyPy
and the separate  py.test tool (used to perform various kinds
of testing in PyPy) during the conference.
-Line 7:
+Line 17:
- * integrating and implementing a full parser/compiler chain written in Python maybe already targetting the new AST-branch of mainline CPython
+Naturally, we are eager to see how the other re-implementation
of Python, namely IronPython, is doing and to explore
collaboration possibilities.  Of course, that will depend on
the degree of openness that Microsoft wants to employ.

The Pycon2005 sprint is going to focus on reaching
compatibility with CPython (currently we target version 2.3.4)
for our PyPy version running on top of CPython. One goal of
the sprint is to pass 60% or more of the unmodified regression
tests of mainline CPython.  It will thus be a great way to get
to know CPython and PyPy better at the same time!  Other
possible work areas include:


 * translation to C to get a first working lower-level representation of the interpreter "specified in Python"

 * integrating and implementing a full parser/compiler chain written in Python perhaps already targetting the new AST-branch of mainline CPython
-Line 11:
+Line 37:
- * we still need a pure python implementation of the following modules.  Anybody see a friend they would like to rewrite?
+ * integrating or coding pure python implementations of some Python modules which are currently written in C.
-Line 13:
+Line 39:
-||_codecsmodule||_hotshot||_localemodule||||_randommodule - exists  with a lesser generator||zipimport||
||_weakref||arraymodule||audioop||binascii||cgensupport||
||cmathmodule||||cryptmodule see: http://home.clear.net.nz/pages/c.evans/sw/ ||gcmodule||imageop||imgfile||
||mathmodule||rgbimgmodule||sgimodule||stropmodule||structmodule||
||symtablemodule||syslogmodule||timingmodule||unicodedata||yuvconvert||
+ * whatever issues you come up with! (but please tell us before hand so we can better plan introductions etc.)
-Line 20:
+Line 43:
-Besides core developers Bea Düring, our "process manager" will be present to help improving and document our sprint and agile development process.
+Besides core developers Bea Düring, our "process manager" will be working off location (IRC/email) during the sprint to help improving and document our sprint and agile development process.
-Line 22:
+Line 45:
-We are going to give tutorials about PyPy's basic concepts and provide help to newcomers usually by pairing them with experienced pypythonistas. However, we ask newcomers to be present on the first day's morning (19th of March) of the sprint to be able to get everyone a smooth start into the sprint. So far most newcomers had few problems in getting a good start into our codebase. However, it is good to have the following preparational points in mind:
+We are going to give tutorials about PyPy's basic concepts and provide help to newcomers usually by pairing them with experienced pypythonistas.   However, we kindly ask newcomers to
be present on the first day's morning (19th of March) of the
sprint to be able to give everyone a smooth start into the
sprint. So far most newcomers have had few problems in getting a
good start into our codebase.  However, it is good to have the
following preparational points in mind:
-Line 26:
+Line 54:
- * subscription to [http://codespeak.net/mailman/listinfo/pypy-dev pypy-dev] and  [http://codespeak.net/mailman/listinfo/pypy-sprint pypy-sprint].
+ * subscription to [[http://codespeak.net/mailman/listinfo/pypy-dev|pypy-dev]] and  [[http://codespeak.net/mailman/listinfo/pypy-sprint|pypy-sprint]].
-Line 30:
+Line 58:
- * have a look at our current [http://codespeak.net/pypy/index.cgi?doc/ documentation], especially the [http://codespeak.net/pypy/index.cgi?doc/architecture architecture] and [http://codespeak.net/pypy/index.cgi?doc/howtopypy getting-started] documents.
+ * have a look at our current [[http://codespeak.net/pypy/index.cgi?doc/|documentation]], especially the [[http://codespeak.net/pypy/index.cgi?doc/architecture|architecture]] and [[http://codespeak.net/pypy/index.cgi?doc/howtopypy|getting-started]] documents.
-Line 32:
+Line 60:
-The pypy-dev and pypy-sprint lists are also the contact points for raising questions and suggesting and discussing sprint topics beforehand.  We are also on #pypy on freenode most of the time. Please don't hesitate to contact us or introduce yourself, your background and your interests at pypy-sprint!
+The pypy-dev and pypy-sprint lists are also the contact points for raising questions and suggesting and discussing sprint topics beforehand.  We are also on #pypy on freenode most of the time. Please don't hesitate to contact us or introduce yourself, your background and your interests!
-Line 34:
+Line 62:
-== Participants ==
+== Logistics ==

Organizational details will be posted to pypy-sprint and are
or will be available in the Pycon2005-Sprint wiki here:

     http://www.python.org/moin/PyConDC2005/Sprints

== Registration ==

send mail to pypy-sprint@codespeak.net, stating the days
you can be present and any specific interests if applicable.

== Registered Participants ==
-Line 38:
+Line 78:
- * Jacob Hallén
+ * Jacob Hallén (Virginian Suites, near Rosslyn)
-Line 42:
+Line 82:
- * Holger Krekel
+ * Samuele Pedroni (Virginian Suites, near Rosslyn)
-Line 44:
+Line 84:
- * Samuele Pedroni
+ * Anders Chrigström (Virginian Suites, near Rosslyn)
-Line 46:
+Line 86:
- * Anders Chrigström
+ * Christian Tismer (Key Bridge, shares with Lutz))
-Line 48:
+Line 88:
- * Bea Düring
+ * Richard Emslie (Econo Lodge Metro, shares with Holger) 

 * Holger Krekel (Econo Lodge Metro, shares with Richard)

 * Lutz Pälike (Key Bridge, shares with Christian)

 * Bob Ippolito

 * Jonathan Riehl

 * Alan Mcintyre (Washington Terrace Hotel)