<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-flowed"
style="font-family: -moz-fixed; font-size: 12px;" lang="x-western">pypy-0.7.0:
first PyPy-generated Python Implementations
<br>
==============================================================
<br>
<br>
What was once just an idea between a few people discussing
<br>
on some nested mailing list thread and in a pub became reality ...
<br>
the PyPy development team is happy to announce its first
<br>
public release of a fully translatable self contained Python
<br>
implementation. The 0.7 release showcases the results of our
<br>
efforts in the last few months since the 0.6 preview release
<br>
which have been partially funded by the European Union:
<br>
<br>
- whole program type inference on our Python Interpreter
<br>
implementation with full translation to two different
<br>
machine-level targets: C and LLVM
<br>
<br>
- a translation choice of using a refcounting or Boehm
<br>
garbage collectors
<br>
<br>
- the ability to translate with or without thread support
<br>
<br>
- very complete language-level compliancy with CPython 2.4.1
<br>
<br>
<br>
What is PyPy (about)?
<br>
------------------------------------------------
<br>
<br>
PyPy is a MIT-licensed research-oriented reimplementation of
<br>
Python written in Python itself, flexible and easy to
<br>
experiment with. It translates itself to lower level
<br>
languages. Our goals are to target a large variety of
<br>
platforms, small and large, by providing a compilation toolsuite
<br>
that can produce custom Python versions. Platform, Memory and
<br>
Threading models are to become aspects of the translation
<br>
process - as opposed to encoding low level details into a
<br>
language implementation itself. Eventually, dynamic
<br>
optimization techniques - implemented as another translation
<br>
aspect - should become robust against language changes.
<br>
<br>
Note that PyPy is mainly a research and development project
<br>
and does not by itself focus on getting a production-ready
<br>
Python implementation although we do hope and expect it to
<br>
become a viable contender in that area sometime next year.
<br>
<br>
<br>
Where to start?
<br>
-----------------------------
<br>
<br>
Getting started: <a class="moz-txt-link-freetext"
href="http://codespeak.net/pypy/dist/pypy/doc/getting-started.html">http://codespeak.net/pypy/dist/pypy/doc/getting-started.html</a>
<br>
<br>
PyPy Documentation: <a class="moz-txt-link-freetext"
href="http://codespeak.net/pypy/dist/pypy/doc/">http://codespeak.net/pypy/dist/pypy/doc/</a>
<br>
<br>
PyPy Homepage: <a class="moz-txt-link-freetext"
href="http://codespeak.net/pypy/">http://codespeak.net/pypy/</a>
<br>
<br>
The interpreter and object model implementations shipped with
<br>
the 0.7 version can run on their own and implement the core
<br>
language features of Python as of CPython 2.4. However, we still
<br>
do not recommend using PyPy for anything else than for education,
<br>
playing or research purposes.
<br>
<br>
Ongoing work and near term goals
<br>
---------------------------------
<br>
<br>
PyPy has been developed during approximately 15 coding sprints
<br>
across Europe and the US. It continues to be a very
<br>
dynamically and incrementally evolving project with many
<br>
one-week meetings to follow. You are invited to consider coming to
<br>
the next such meeting in Paris mid October 2005 where we intend to
<br>
plan and head for an even more intense phase of the project
<br>
involving building a JIT-Compiler and enabling unique
<br>
features not found in other Python language implementations.
<br>
<br>
PyPy has been a community effort from the start and it would
<br>
not have got that far without the coding and feedback support
<br>
from numerous people. Please feel free to give feedback and
<br>
raise questions.
<br>
<br>
contact points: <a class="moz-txt-link-freetext"
href="http://codespeak.net/pypy/dist/pypy/doc/contact.html">http://codespeak.net/pypy/dist/pypy/doc/contact.html</a>
<br>
<br>
contributor list: <a class="moz-txt-link-freetext"
href="http://codespeak.net/pypy/dist/pypy/doc/contributor.html">http://codespeak.net/pypy/dist/pypy/doc/contributor.html</a>
<br>
<br>
have fun,
<br>
<br>
the pypy team, of which here is a partial snapshot
<br>
of mainly involved persons:
<br>
<br>
Armin Rigo, Samuele Pedroni,
<br>
Holger Krekel, Christian Tismer,
<br>
Carl Friedrich Bolz, Michael Hudson,
<br>
Eric van Riet Paap, Richard Emslie,
<br>
Anders Chrigstroem, Anders Lehmann,
<br>
Ludovic Aubry, Adrien Di Mascio,
<br>
Niklaus Haldimann, Jacob Hallen,
<br>
Bea During, Laura Creighton,
<br>
and many contributors ...
<br>
<br>
PyPy development and activities happen as an open source project
<br>
and with the support of a consortium partially funded by a two
<br>
year European Union IST research grant. Here is a list of
<br>
the full partners of that consortium:
<br>
<br>
Heinrich-Heine University (Germany), AB Strakt (Sweden)
<br>
merlinux GmbH (Germany), tismerysoft GmbH(Germany)
<br>
Logilab Paris (France), DFKI GmbH (Germany)
<br>
ChangeMaker (Sweden), Impara (Germany)
<br>
</div>
</body>
</html>