jc211

tractor

'structured concurrent `trio`-"actors"'

Go to file

Tyler Goodlet 2ccaa94c60 Move daemon fixture up to conftest		2020-08-03 15:39:54 -04:00
docs	Set correct master doc name	2020-02-10 12:26:19 -05:00
examples	Move two more examples out of docs for testing	2020-02-10 12:14:16 -05:00
tests	Move daemon fixture up to conftest	2020-08-03 15:39:54 -04:00
tractor	Docstring to the top\!, and redundant spaces goodbye\!	2020-07-29 15:39:38 -03:00
.gitignore	Initial commit	2018-07-05 16:01:15 -04:00
.travis.yml	Finally tame the super flaky tests	2020-07-26 22:53:40 -04:00
LICENSE	Initial commit	2018-07-05 16:01:15 -04:00
README.rst	Drop sphinx toctree from readme	2020-02-10 12:14:16 -05:00
mypy.ini	Add mypy.ini lel	2020-01-21 15:28:12 -05:00
requirements-test.txt	More mypy apeasement on 3.7	2020-01-15 21:06:13 -05:00
setup.py	Actually dropping the cloudpickle dependency from setup.py	2020-07-27 21:10:04 -03:00

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.git

Feel 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!