Differences between revisions 70 and 71
Revision 70 as of 2012-04-29 19:08:47
Size: 8664
Editor: PaulBoddie
Comment: Added academic projects.
Revision 71 as of 2012-05-02 15:41:18
Size: 9035
Editor: PaulBoddie
Comment: Divided the implementations into two groups, moved the GCC Python Front-End into the compilers section.
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * [[http://code.google.com/p/unladen-swallow/|unladen-swallow]] - "an optimization branch of CPython, intended to be fully compatible and significantly faster", originally considered for merging with CPython subject to PEP PEP:3146, but now unmaintained  * [[http://code.google.com/p/unladen-swallow/|unladen-swallow]] - "an optimization branch of CPython, intended to be fully compatible and significantly faster", originally considered for merging with CPython subject to [[PEP:3146|PEP 3146]], but now unmaintained
Line 23: Line 23:
Note that most of these project have not yet achieved language compliance. However, many of these have goals and features or run in certain environments that make them interesting in their own regard. The only implementations that are known to be compatible with a given version of the language are IronPython, [[Jython]] and PyPy. Note that most of these projects have not yet achieved language compliance. However, many of these have goals and features or run in certain environments that make them interesting in their own regard. The only implementations that are known to be compatible with a given version of the language are IronPython, [[Jython]] and PyPy.
Line 25: Line 25:
 * [[http://wiki.github.com/bjpop/berp/|Berp]] - an implementation of Python 3 in Haskell, providing an interactive environment as well as a compiler === Working Implementations ===

The following implementations may be comprehensive or even complete, but at the very least can be said to be working in that you can run typical programs with them already:
Line 27: Line 30:
 * [[http://gcc.gnu.org/wiki/PythonFrontEnd|GCC Python Front-End]] - an in-progress effort to compile Python code within the GCC infrastructure
Line 31: Line 33:
 * [[http://pyjs.org/|pyjamas]] - a Python to !JavaScript compiler plus Web/GUI framework
Line 33: Line 36:
 * [[http://pyjs.org/|pyjamas]] - a Python to !JavaScript compiler plus Web/GUI framework
 * [[http://code.google.com/p/pystachio/|Pystacho]] is, like Skulpt, Python in !JavaScript
Line 36: Line 37:
 * [[http://www.skulpt.org/|Skulpt]] - Python in !JavaScript
Line 39: Line 39:

=== Tentative Implementations ===

The following implementations are apparent works in progress; they may not be able to run typical programs:

 * [[http://wiki.github.com/bjpop/berp/|Berp]] - an implementation of Python 3 in Haskell, providing an interactive environment as well as a compiler
 * [[http://code.google.com/p/pystachio/|Pystacho]] is, like Skulpt, Python in !JavaScript
 * [[http://www.skulpt.org/|Skulpt]] - Python in !JavaScript
Line 54: Line 62:
 * [[http://gcc.gnu.org/wiki/PythonFrontEnd|GCC Python Front-End]] - an in-progress effort to compile Python code within the GCC infrastructure

Python Implementations

An "implementation" of Python should be taken to mean a program or environment which provides support for the execution of programs written in the Python language, as represented by the CPython reference implementation.

There have been and are several distinct software packages providing of what we all recognize as Python, although some of those are more like distributions or variants of some existing implementation than a completely new implementation of the language.

CPython Variants

These are implementations based on the CPython runtime core (the de-facto reference Python implementation), but with extended behaviour or features in some aspects.

  • CrossTwine Linker - a combination of CPython and an add-on library offering improved performance (currently proprietary)

  • Stackless Python - CPython with an emphasis on concurrency using tasklets and channels (used by dspython for the Nintendo DS)

  • unladen-swallow - "an optimization branch of CPython, intended to be fully compatible and significantly faster", originally considered for merging with CPython subject to PEP 3146, but now unmaintained

  • wpython - a re-implementation of CPython using "wordcode" instead of bytecode

Other Implementations

These are re-implementations of the Python language that do not depend on (or necessarily interact with) the CPython runtime core. Many of them reuse (a large part of) the standard library implementation.

Note that most of these projects have not yet achieved language compliance. However, many of these have goals and features or run in certain environments that make them interesting in their own regard. The only implementations that are known to be compatible with a given version of the language are IronPython, Jython and PyPy.

Working Implementations

The following implementations may be comprehensive or even complete, but at the very least can be said to be working in that you can run typical programs with them already:

  • CLPython - Python in Common Lisp

  • HotPy - a virtual machine for Python supporting bytecode optimisation and translation (to native code) using type information gathered at run-time

  • IronPython - Python in C# for the Common Language Runtime (CLR/.NET) and the FePy project's IronPython Community Edition (IPCE)

  • Jython - Python in Java for the Java platform

  • pyjamas - a Python to JavaScript compiler plus Web/GUI framework

  • PyMite - Python for embedded devices

  • PyPy - Python in Python, targeting several environments

  • pyvm - a Python-related virtual machine and software suite providing a nearly self-contained "userspace" system

  • SNAPpy - "a subset of the Python language that has been optimized for use in low-power embedded devices" (apparently proprietary)

  • tinypy - a minimalist implementation of python in 64k of code

Tentative Implementations

The following implementations are apparent works in progress; they may not be able to run typical programs:

  • Berp - an implementation of Python 3 in Haskell, providing an interactive environment as well as a compiler

  • Pystacho is, like Skulpt, Python in JavaScript

  • Skulpt - Python in JavaScript

  • Typhon - a Rubinius-based implementation of Python

Extensions

These are typically part of CPython (or some other implementation) but change the implementation's behaviour:

  • Psyco - a just-in-time specialising compiler for CPython

Compilers

These compilers usually implement something close to Python, although some compilers may impose restrictions that alter the nature of the language:

  • 2c-python - a static Python-to-C compiler, apparently translating CPython bytecode to C

  • Compyler - an attempt to "transliterate the bytecode into x86 assembly" (now abandoned)

  • Cython - an optimising Python-to-C compiler, CPython extension module generator, and wrapper language for binding external libraries. Interacts with CPython runtime and supports embedding CPython in stand-alone binaries.

  • GCC Python Front-End - an in-progress effort to compile Python code within the GCC infrastructure

  • Nuitka - a Python-to-C++ compiler using libpython at run-time, attempting some compile-time and run-time optimisations. Interacts with CPython runtime.

  • Pyc - performs static analysis in order to compile Python programs, uses similar techniques to Shed Skin

  • Shed Skin - a Python-to-C++ compiler, restricted to an implicitly statically typed subset of the language for which it can automatically infer efficient types through whole program analysis

  • unPython - a Python to C compiler using type annotations

Similar but Distinct Languages

These languages don't attempt to be directly compatible even with a subset of Python, choosing to provide their own set of features:

  • Boo

  • Cobra

  • Converge - inspired by Python, Haskell, Icon and Smalltalk, provides macros which can be evaluated at compile-time

  • Delight - based on the D programming language

  • Genie - based on the same foundations (Gtk+, GNOME) as the Vala programming language, supposedly inspired by Boo

  • Mython - an extensible variant of the Python programming language, apparently a front-end for CPython

  • Nimrod - statically typed, compiles to C, features parameterised types, macros, and so on

  • Pythonect - a dataflow-oriented language adopting the basic Python expression syntax, implemented in Python and integrated with the Python environment

  • Serpent - inspired by Python, supporting real-time garbage collection and multiple virtual machines in separate threads (more information)

  • Trylon - inspired heavily by Smalltalk

  • Wirbel - a compilable language with similar restrictions to Shed Skin (statically typed names, lists cannot mix elements of different types), no longer actively developed as of 2011-07-21

Comparisons:

Topic Guides

(Fun) Python Preprocessors

There are even some tongue-in-cheek dialects of Python which you might find fun.

Academic Projects

Python implementations and compilers have been the topic of various papers and theses. Those that have not apparently been developed further are listed here:


This page aims to replace one formerly maintained as "Cameron Laird's personal notes on varieties of Python implementation". Also of interest will be IntegratingPythonWithOtherLanguages, which, among other variants, mentions embeddings of Python in other languages.


CategoryImplementations

PythonImplementations (last edited 2023-06-24 04:21:27 by MaxBernstein)

Unable to edit the page? See the FrontPage for instructions.