f05534e472
This begins the move to dropping support for `tractor.run()` which we don't really need since the runtime is started (as it always has been) from a new sub-task / nursery. Instead this introduces starting the actor tree through a `open_root_actor()` async context manager which we'll likely implicitly call (from the root) on the first use of an actor nursery. Drop `_actor._start_actor()` and factor its contents into this new api. Make `run()` and `run_daemon()` use `open_root_actor()` until we decide to remove them. Relates to #168 and #177 |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| examples | ||
| tests | ||
| tractor | ||
| .gitignore | ||
| LICENSE | ||
| README.rst | ||
| mypy.ini | ||
| requirements-docs.txt | ||
| requirements-test.txt | ||
| setup.py | ||
README.rst
tractor
A structured concurrent, async-native "actor model" built on trio and multiprocessing.
tractor is an attempt to bring trionic structured concurrency to distributed multi-core Python; it aims to be the Python multi-processing framework you always wanted.
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.
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 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 on in our matrix channel. If matrix seems too hip, we're also mostly all in the the trio gitter channel!