Welcome to PyPy Development
The PyPy project aims at producing a flexible and fast Python implementation. The guiding idea is to translate a Python-level description of the Python language itself to lower level languages. Rumors have it that the secret goal is being faster-than-C which is nonsense, isn't it? more...
Getting into PyPy ...
- Getting started: how to install and run the PyPy Python interpreter
- FAQ: some frequently asked questions.
- Release 2.0 beta 1: the latest official release
- PyPy Blog: news and status info about PyPy
- Papers: Academic papers, talks, and related projects
- speed.pypy.org: Daily benchmarks of how fast PyPy is
- potential project ideas: In case you want to get your feet wet...
Documentation for the PyPy Python Interpreter
New features of PyPy's Python Interpreter and Translation Framework:
Status of the project.
Mailing lists, bug tracker, IRC channel
- Development mailing list: development and conceptual discussions.
- Mercurial commit mailing list: updates to code and documentation.
- Development bug/feature tracker: filing bugs and feature requests.
- IRC channel #pypy on freenode: Many of the core developers are hanging out at #pypy on irc.freenode.net. You are welcome to join and ask questions (if they are not already developed in the FAQ). You can find logs of the channel here.
Meeting PyPy developers
The PyPy developers are organizing sprints and presenting results at conferences all year round. They will be happy to meet in person with anyone interested in the project. Watch out for sprint announcements on the development mailing list.
PyPy was funded by the EU for several years. See the web site of the EU project for more details.
architecture gives a complete view of PyPy's basic design.
coding guide helps you to write code for PyPy (especially also describes coding in RPython a bit).
sprint reports lists reports written at most of our sprints, from 2003 to the present.
papers, talks and related projects lists presentations and related projects as well as our published papers.
PyPy video documentation is a page linking to the videos (e.g. of talks and introductions) that are available.
Technical reports is a page that contains links to the reports that we submitted to the European Union.
development methodology describes our sprint-driven approach.
LICENSE contains licensing details (basically a straight MIT-license).
Glossary of PyPy words to help you align your inner self with the PyPy universe.
PyPy can be used to run Python programs on Linux, OS/X, Windows, on top of .NET, and on top of Java. To dig into PyPy it is recommended to try out the current Mercurial default branch, which is always working or mostly working, instead of the latest release, which is 2.0 beta1.
PyPy is mainly developed on Linux and Mac OS X. Windows is supported, but platform-specific bugs tend to take longer before we notice and fix them. Linux 64-bit machines are supported (though it may also take some time before we notice and fix bugs).
PyPy's own tests summary, daily updated, run through BuildBot infrastructure. You can also find CPython's compliance tests run with compiled pypy-c executables there.
Source Code Documentation
object spaces discusses the object space interface and several implementations.
bytecode interpreter explains the basic mechanisms of the bytecode interpreter and virtual machine.
interpreter optimizations describes our various strategies for improving the performance of our interpreter, including alternative object implementations (for strings, dictionaries and lists) in the standard object space.
garbage collector strategies that can be used by the virtual machines produced by the translation process.
parser contains (outdated, unfinished) documentation about the parser.
rlib describes some modules that can be used when implementing programs in RPython.
configuration documentation describes the various configuration options that allow you to customize PyPy.
CLI backend describes the details of the .NET backend.
JIT Generation in PyPy describes how we produce the Python Just-in-time Compiler from our Python interpreter.
PyPy directory cross-reference
Here is a fully referenced alphabetical two-level deep directory overview of PyPy:
|`pypy/bin/`_||command-line scripts, mainly `pypy/bin/pyinteractive.py`_|
|`pypy/config/`_||handles the numerous options for building and running PyPy|
|`pypy/doc/`_||text versions of PyPy developer documentation|
|`pypy/doc/config/`_||documentation for the numerous translation options|
|`pypy/doc/discussion/`_||drafts of ideas and documentation|
|doc/*/||other specific documentation topics or tools|
|`pypy/interpreter/`_||bytecode interpreter and related objects (frames, functions, modules,...)|
|`pypy/interpreter/pyparser/`_||interpreter-level Python source parser|
|`pypy/interpreter/astcompiler/`_||interpreter-level bytecode compiler, via an AST representation|
|`pypy/module/`_||contains mixed modules implementing core modules with both application and interpreter level code. Not all are finished and working. Use the --withmod-xxx or --allworkingmodules translation options.|
|`pypy/objspace/`_||object space implementations|
|`pypy/objspace/std/`_||the StdObjSpace implementing CPython's objects and types|
|`pypy/tool/`_||various utilities and hacks used from various places|
|`pypy/tool/algo/`_||general-purpose algorithmic and mathematic tools|
|`pypy/tool/pytest/`_||support code for our testing methods|
|`rpython/annotator/`_||type inferencing code for RPython programs|
|`rpython/config/`_||handles the numerous options for RPython|
|`rpython/flowspace/`_||the FlowObjSpace implementing abstract interpretation|
|`rpython/rlib/`_||a "standard library" for RPython programs|
|`rpython/rtyper/`_||the RPython Typer|
|`rpython/rtyper/lltypesystem/`_||the low-level type system for C-like backends|
|`rpython/rtyper/ootypesystem/`_||the object-oriented type system for OO backends|
|`rpython/memory/`_||the garbage collector construction framework|
|`rpython/translator/`_||translation backends and support code|
|`rpython/translator/backendopt/`_||general optimizations that run before a backend generates code|
|`rpython/translator/c/`_||the GenC backend, producing C code from an RPython program (generally via the rtyper)|
|`rpython/translator/cli/`_||the CLI backend for .NET (Microsoft CLR or Mono)|
|`pypy/goal/`_||our main PyPy-translation scripts live here|
|`rpython/translator/jvm/`_||the Java backend|
|`rpython/translator/tool/`_||helper tools for translation|
|*/test/||many directories have a test subdirectory containing test modules (see Testing in PyPy)|
|_cache/||holds cache files from various purposes|