|This article's lead section may not adequately summarize key points of its contents. (January 2017)|
|Initial release||mid 2007|
5.6.0 / 12 November 2016
|Type||Python interpreter and compiler toolchain|
PyPy started out as a Python interpreter written in the Python language itself. Current PyPy versions are translated into an intermediate representation, RPython, into C code, and then compiled. The PyPy JIT compiler processes this into machine code at run time.
Details and motivation
PyPy was conceived to be an implementation of Python written in a programming language that is similar to Python. This makes it easy to identify areas where it can be improved and makes PyPy more flexible and easier to experiment with than CPython.
PyPy aims to provide a common translation and support framework for producing implementations of dynamic languages, emphasizing a clean separation between language specification and implementation aspects. It also aims to provide a compliant, flexible and fast implementation of the Python programming language using the above framework to enable new advanced features without having to encode low level details into it.
The PyPy interpreter itself is written in a restricted subset of Python, called RPython (Restricted Python). The self-hosting nature of PyPy is reflected in the project's logo, which depicts a snake swallowing its own tail in an ouroboros. RPython puts some constraints on the Python language such that a variable's type can be inferred at compile time.
The PyPy project has developed a toolchain that analyzes RPython code and translates it into C code, which is then compiled to produce a native interpreter. It also allows for pluggable garbage collectors as well as optionally enabling Stackless Python features. Finally, it includes a just-in-time (JIT) generator which builds a just-in-time compiler into the interpreter, given a few annotations in the interpreter source code. The generated JIT compiler is a tracing JIT.
PyPy is CPython 2.7.10 compatible. PyPy3, released starting with version 2.3.1, is CPython 3.2.5 compatible. Both versions have JIT compilation support on 32-bit/64-bit x86 and ARM processors. It is tested nightly on Windows, Linux, OpenBSD and Mac OS X. PyPy is able to run pure Python software that does not rely on implementation-specific features.
There is a compatibility layer for CPython C API extensions called CPyExt, but it is incomplete and experimental. The preferred way of interfacing with C shared libraries is through the built-in CFFI or ctypes libraries.
PyPy was initially a research and development-oriented project. Reaching a mature state of development and an official 1.0 release in mid-2007, its next focus was on releasing a production-ready version with more CPython compatibility. Many of PyPy's changes have been made during coding sprints.
In March 2010, PyPy 1.2 was released, focusing on speed. It included a working, though not yet stable, just-in-time compiler.
In April 2011, PyPy version 1.5 was released, which reached compatibility with CPython 2.7.
On May 9, 2013, PyPy 2.0 was released, which introduced alpha-quality support for JIT compilation on ARMv6 and ARMv7 JIT, and included CFFI in the standard library.
On June 20, 2014, PyPy3 was declared stable and introduced compatibility with the more modern Python 3. It was released alongside PyPy 2.3.1 and bears the same version number.
PyPy was funded by the European Union being a Specific Targeted Research Project between December 2004 and March 2007. In June 2008, PyPy announced funding being part of the Google Open Source programs, and has agreed to focus on making PyPy more compatible with CPython. In 2009 Eurostars, a European Union funding agency specially focused on SMEs, accepted a proposal from PyPy project members entitled: "PYJIT - a fast and flexible toolkit for dynamic programming languages based on PyPy". Eurostars funding lasted until August 2011. At PyCon US 2011, the Python Software Foundation provided a $10,000 grant for PyPy to continue work on performance and compatibility with newer versions of the language. The port to ARM architecture was sponsored in part by the Raspberry Pi Foundation.
The PyPy project also accepts donations through its status blog pages. There are three funding projects currently in progress: Python 3 version compatibility, built-in optimized NumPy support for numerical calculations and software transactional memory support to allow better parallelism.
- Bootstrapping (compilers)
- Partial evaluation
- Pixie (programming language)
- Unladen Swallow
- Graal (compiler)#Truffle
- Samuele Pedroni (March 2007). "PyPy - Goals and Architecture Overview".
- "PyPy - Goals and Architecture Overview - Mission Statement". Retrieved 11 October 2013.
- Our runtime interpreter is “RPython”, Coding Guide — PyPy documentation
- "It is a proper subset of Python, restricted in a way that enables easy analysis and efficient code generation", Ancona et al., 2007.
- Bolz, Carl; Cuni, Antonio; Fijalkowski, Maciej; Rigo, Armin. Tracing the Meta-Level: PyPy’s Tracing JIT Compiler. ICOOOLPS '09. doi:10.1145/1565824.1565827.
- Timothy Balridge interview
- "PyPy - Python compatibility". pypy.org. Retrieved 2016-04-21.
- the PyPy team (20 June 2014). "PyPy3 2.3.1 - Fulcrum". PyPy blog.
- Jake Edge (15 May 2013). "A look at the PyPy 2.0 release". LWN.net.
- "PyPy - Python compatibility".
- "Running pylons on top of PyPy".
- "Running Pyglet on top of PyPy".
- "Running Nevow on top of PyPy".
- "PyPy runs unmodified django 1.0 beta".
- "EU Community Research and Development Information Service Entry".
- "Eurostars - Aim Higher".
- "Project Page on Eureka Network".
- "A thank you to the PSF".
- "PyPy Status Blog: Oh, and btw: PyPy gets funding through "Eurostars"".
- Davide Ancona, Massimo Ancona, Antonio Cuni, Nicholas D. Matsakis, 2007. RPython: a Step Towards Reconciling Dynamically and Statically Typed OO Languages. In Proc. Dynamic Language Symposium (DLS), 2007. ACM Press.
- Carl Friedrich Bolz, Antonio Cuni, Maciej Fijalkowski, 2009. Tracing the meta-level: PyPy's Tracing JIT Compiler. In Proc. ICOOOLPS, 2009. ACM Press.
- Corbet, Jonathan (May 11, 2011). "A brief experiment with PyPy". LWN.net.
- von Eitzen, Chris (November 21, 2011). "PyPy 1.7 widens the performance "sweet spot"". The H. Heinz Heise.
- Rose, John (December 2, 2011). "A Day with PyPy". Oracle developer blog.
- "Interview Maciej Fijalkowski pypy". Decisionstats blog.