Mypy Development Roadmap

Phase 1: Type checker and mypy-to-Python translator [FINISHED]

Implement type checker for a significant subset of mypy. Support running mypy programs via translation to Python + using CPython (perhaps also PyPy, if Python 2/3 compatibility can be addressed).

The implementation will be good for early adopters and for the evaluation of the programming model.

Mypy development will be mostly done in mypy after this phase (also use C for VM facilities, gc, C API and low-level libraries). Before the switch to mypy is ready, development will be in Alore (that's also why there is no code initially; there will be a switch from Alore to mypy using an automated translator, which would break all branches and could cause all kinds of trouble if not managed carefully).

Schedule: Nov 2012 [FINISHED]

Phase 2: Self-compilation to native code

Implement a native code compiler for a useful mypy subset. Also add support for essential Python libraries. The compiler should be good enough to compile itself and give a major performance boost compared to CPython (and PyPy, unless we can't support a PyPy backend due to Python 2/3 issues).

Schedule: 2013

Phase 3: More Python features

The focus is on supporting a wider set of Python features and libraries.

Schedule: ?

Future tasks

These tasks have not been scheduled yet. Some of these are basically wishlist items without any concrete plans yet.