forked from goodboy/tractor
1
0
Fork 0
tractor/docs/README.rst

104 lines
4.3 KiB
ReStructuredText
Raw Normal View History

tractor
=======
2020-10-14 15:07:48 +00:00
The Python async-native multi-core system *you always wanted*.
2020-10-14 01:33:22 +00:00
|gh_actions|
|docs|
2020-02-10 16:49:54 +00:00
.. _actor model: https://en.wikipedia.org/wiki/Actor_model
.. _trio: https://github.com/python-trio/trio
2020-12-09 18:01:57 +00:00
.. _multi-processing: https://en.wikipedia.org/wiki/Multiprocessing
2020-02-10 16:49:54 +00:00
.. _trionic: https://trio.readthedocs.io/en/latest/design.html#high-level-design-principles
.. _async sandwich: https://trio.readthedocs.io/en/latest/tutorial.html#async-sandwich
.. _structured concurrent: https://trio.discourse.group/t/concise-definition-of-structured-concurrency/228
2020-12-09 18:01:57 +00:00
``tractor`` is a `structured concurrent`_ "`actor model`_" built on trio_ and multi-processing_.
2020-10-14 15:07:48 +00:00
It is an attempt to pair trionic_ `structured concurrency`_ with
2020-12-09 18:01:57 +00:00
distributed Python. You can think of it as a ``trio``
*-across-processes* or simply as an opinionated replacement for the
stdlib's ``multiprocessing`` but built on async programming primitives
from the ground up.
2020-10-14 15:07:48 +00:00
2020-12-09 18:01:57 +00:00
Don't be scared off by this description. ``tractor`` **is just ``trio``**
but with nurseries for process management and cancel-able IPC.
If you understand how to work with ``trio``, ``tractor`` will give you
the parallelism you've been missing.
``tractor``'s nurseries let you spawn ``trio`` *"actors"*: new Python
2020-10-14 15:07:48 +00:00
processes which each run a ``trio`` scheduled task tree (also known as
2020-12-09 18:01:57 +00:00
an `async sandwich`_ - a call to ``trio.run()``). That is, each
"*Actor*" is a new process plus a ``trio`` runtime.
2020-12-09 18:01:57 +00:00
"Actors" communicate by exchanging asynchronous messages_ and avoid
2020-10-14 15:07:48 +00:00
sharing state. The intention of this model is to allow for highly
distributed software that, through the adherence to *structured
2020-12-09 18:01:57 +00:00
concurrency*, results in systems which fail in predictable and
recoverable ways.
2019-03-07 02:30:00 +00:00
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`_.
.. _messages: https://en.wikipedia.org/wiki/Message_passing
.. _trio docs: https://trio.readthedocs.io/en/latest/
.. _blog post: https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
2018-09-21 00:30:57 +00:00
.. _structured concurrency: https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
2020-02-10 16:49:54 +00:00
.. _3 axioms: https://en.wikipedia.org/wiki/Actor_model#Fundamental_concepts
.. _unrequirements: https://en.wikipedia.org/wiki/Actor_model#Direct_communication_and_asynchrony
.. _async generators: https://www.python.org/dev/peps/pep-0525/
2019-01-21 16:56:33 +00:00
Install
-------
No PyPi release yet!
::
2019-04-28 14:41:24 +00:00
pip install git+git://github.com/goodboy/tractor.git
2020-10-14 15:07:48 +00:00
Alluring Features
-----------------
2020-12-09 18:01:57 +00:00
- **It's just** ``trio``, but with SC applied to processes (aka "actors")
2020-10-14 15:07:48 +00:00
- Infinitely nesteable process trees
2020-12-09 18:01:57 +00:00
- Built-in API for inter-process streaming
2020-10-14 15:07:48 +00:00
- A (first ever?) "native" multi-core debugger for Python using `pdb++`_
2020-12-09 18:01:57 +00:00
- (Soon to land) ``asyncio`` support allowing for "infected" actors where
2020-10-14 15:07:48 +00:00
`trio` drives the `asyncio` scheduler via the astounding "`guest mode`_"
2020-12-09 18:01:57 +00:00
The example you're probably after...
------------------------------------
It seems the initial query from most new users is "how do I make a worker
pool thing?".
``tractor`` is built to handle any SC process tree you can
imagine; the "worker pool" pattern is a trivial special case:
# TODO: workerpool example
2019-01-17 04:19:29 +00:00
Feel like saying hi?
--------------------
This project is very much coupled to the ongoing development of
2020-09-24 14:04:56 +00:00
``trio`` (i.e. ``tractor`` gets most of its ideas from that brilliant
2019-01-17 04:19:29 +00:00
community). If you want to help, have suggestions or just want to
2020-10-14 15:07:48 +00:00
say hi, please feel free to reach us in our `matrix channel`_. If
2020-09-24 14:04:56 +00:00
matrix seems too hip, we're also mostly all in the the `trio gitter
channel`_!
2019-01-17 04:19:29 +00:00
.. _trio gitter channel: https://gitter.im/python-trio/general
2020-09-24 14:04:56 +00:00
.. _matrix channel: https://matrix.to/#/!tractor:matrix.org
2020-10-14 15:07:48 +00:00
.. _pdb++: https://github.com/pdbpp/pdbpp
.. _guest mode: https://trio.readthedocs.io/en/stable/reference-lowlevel.html?highlight=guest%20mode#using-guest-mode-to-run-trio-on-top-of-other-event-loops
2020-02-10 16:49:54 +00:00
2020-10-14 01:33:22 +00:00
.. |gh_actions| image:: https://img.shields.io/endpoint.svg?url=https%3A%2F%2Factions-badge.atrox.dev%2Fgoodboy%2Ftractor%2Fbadge&style=popout-square
:target: https://actions-badge.atrox.dev/goodboy/tractor/goto
2020-02-10 16:49:54 +00:00
.. |docs| image:: https://readthedocs.org/projects/tractor/badge/?version=latest
:target: https://tractor.readthedocs.io/en/latest/?badge=latest
:alt: Documentation Status