Kevin Quick

Thank you for the appreciation: it's nice to know when Thespian is useful. Regarding your issues, let me first say that I don't have any Windows systems conveniently available, so...

Hi @rifoerster , It would be great if you were able to reproduce this with a simple Actor or set of Actors that you could then attach to this issue...

The TCP protocol is a streaming protocol, so in order for Thespian to reconstruct a message from the byte stream and confirm that reception, there is some bidirectional communication over...

There is currently no system base implemented on top of a message bus implementation (see also https://thespianpy.com/doc/using.html#hH-4f420b34-24a5-49a0-b70b-e34a925e7c17).

See also https://github.com/kquick/Thespian/issues/47

Hi @carlos-lm , Thanks for the appreciation: it's nice to know this library has been useful. You will almost certainly want to use one of the multi-process bases; I would...

That warning is described here: https://github.com/kquick/Thespian/issues/11 Thespian uses the Python `pickle` facility to pass objects. As long as your message can be pickled, Thespian can pass it, although your intuition...

It's hard to say what your issue might be from the code fragments above, but I can make some observations about things that you should probably change: The actor's `receiveMessage`...

When you startup an `ActorSystem`1 with one of the multiproc bases, that ActorSystem will fork and run as a separate process. That process will continue to run until it is...

Killing the other app on port 1900 should open it up to use by Thespian, but that assumes the other app is not needed (and if so, it might be...