f1b242f913
This seems to prevent a certain class of bugs to do with the root actor cancelling local tasks and getting into deadlock while children are trying to acquire the tty lock. I'm not sure it's the best idea yet since you're pretty much guaranteed to get "stuck" if a child activates the debugger after the root has been cancelled (at least "stuck" in terms of SIGINT being ignored). That kinda race condition seems to still exist somehow: a child can "beat" the root to activating the tty lock and the parent is stuck waiting on the child to terminate via its nursery. |
||
|---|---|---|
| .github/workflows | ||
| debugging | ||
| docs | ||
| examples | ||
| tests | ||
| tractor | ||
| .gitignore | ||
| .travis.yml | ||
| 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 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!