Mypyc is not yet useful for general Python development.
Mypyc is a compiler that compiles mypy-annotated, statically typed Python modules into Python C extensions. Currently our focus is on making mypy faster through compilation.
-
macOS Sierra or later
-
Xcode command line tools
-
Python 3.6 (64-bit) from python.org (other versions likely won't work right now)
-
A recent enough C/C++ build environment
-
Python 3.5+ (64-bit)
-
Windows has been tested with Windows 10 and MSVC 2017.
-
Python 3.5+ (64-bit)
First clone the mypyc git repository and git submodules:
$ git clone --recurse-submodules https://github.com/mypyc/mypyc.git
$ cd mypyc
Optionally create a virtualenv (recommended):
$ virtualenv -p python3 <directory>
$ source <directory>/bin/activate
Then install the dependencies:
$ python3 -m pip install -r mypyc/external/mypy/test-requirements.txt
Now you can run the tests:
$ pytest mypyc
Look at the issue tracker for things to work on. Please express your interest in working on an issue by adding a comment before doing any significant work, since development is currently very active and there is real risk of duplicate work.
We have some developer documentation.
These are the current planned major milestones:
-
[DONE] Support a smallish but useful Python subset. Focus on compiling single modules, while the rest of the program is interpreted and does not need to be type checked.
-
[DONE] Support compiling multiple modules as a single compilation unit (or dynamic linking of compiled modules). Without this inter-module calls will use slower Python-level objects, wrapper functions and Python namespaces.
-
[DONE] Mypyc can compile mypy.
-
[DONE] Optimize some important performance bottlenecks.
-
Generate useful errors for code that uses unsupported Python features instead of crashing or generating bad code.
-
Release a version of mypy that includes a compiled mypy.
We have some ideas for future improvements and optimizations.