d6abfa774a
|
||
|---|---|---|
| docs | ||
| examples | ||
| tests | ||
| tractor | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| README.rst | ||
| mypy.ini | ||
| requirements-test.txt | ||
| setup.py | ||
README.rst
tractor
An async-native "actor model" built on trio and multiprocessing.
tractor is an attempt to bring trionic structured concurrency to distributed multi-core Python.
tractor lets you spawn trio "actors": processes which each run a trio scheduled task tree (also known as an async sandwich). Actors communicate by exchanging asynchronous messages and avoid sharing any state. This model allows for highly distributed software architecture which works just as well on multiple cores as it does over many hosts.
The first step to grok tractor is to get the basics of trio down. A great place to start is the trio docs and this blog post.
Philosophy
tractor aims to be the Python multi-processing framework you always wanted.
Its tenets non-comprehensively include:
- strict adherence to the concept-in-progress of structured concurrency
- no spawning of processes willy-nilly; causality is paramount!
- (remote) errors always propagate back to the parent supervisor
- verbatim support for
trio's cancellation system - shared nothing architecture
- no use of proxy objects or shared references between processes
- an immersive debugging experience
- anti-fragility through chaos engineering
Warning
tractor is in alpha-alpha and is expected to change rapidly! Expect nothing to be set in stone. Your ideas about where it should go are greatly appreciated!
Install
No PyPi release yet!
pip install git+git://github.com/goodboy/tractor.gitFeel like saying hi?
This project is very much coupled to the ongoing development of trio (i.e. tractor gets all its ideas from that brilliant community). If you want to help, have suggestions or just want to say hi, please feel free to ping me on the trio gitter channel!