0a5a4d8487
|
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| examples | ||
| tests | ||
| tractor | ||
| .gitignore | ||
| LICENSE | ||
| mypy.ini | ||
| requirements-docs.txt | ||
| requirements-test.txt | ||
| setup.py | ||
docs/README.rst
tractor
The Python async-native multi-core system you always wanted.
tractor is a structured concurrent "actor model" built on trio and multiprocessing.
It is an attempt to pair trionic structured concurrency with distributed Python. You can think of it as a trio -across-processes or simply as a replacement for the stdlib's multiprocessing but built on async primitives for IPC.
tractor's nurseries lets you spawn trio "actors": new Python processes which each run a trio scheduled task tree (also known as an async sandwich). That is, each "Actor" is a new process plus a trio runtime.
Processes communicate by exchanging asynchronous messages and avoid sharing state. The intention of this model is to allow for highly distributed software that, through the adherence to structured concurrency, results in systems which fail in predicatable ways.
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.
Install
No PyPi release yet!
pip install git+git://github.com/goodboy/tractor.gitAlluring Features
- Infinitely nesteable process trees
- A built-in API for inter-process streaming
- A (first ever?) "native" multi-core debugger for Python using pdb++
- (Soon to land) asyncio support allowing for "infected" actors where trio drives the asyncio scheduler via the astounding "guest mode"
Feel like saying hi?
This project is very much coupled to the ongoing development of trio (i.e. tractor gets most of its ideas from that brilliant community). If you want to help, have suggestions or just want to say hi, please feel free to reach us in our matrix channel. If matrix seems too hip, we're also mostly all in the the trio gitter channel!