Kevin Quick

Thank you for posting issues: they all help to improve Thespian in some way! You've encountered a bit of a tricky support contortions in the networking support: namely that each...

Hi @asomov, Thespian handles actor relationships slightly differently than the Erlang/OTP, but you should have all the same functionality available in both systems. In Thespian, the Parent actor acts as...

Hi @asomov , I'm happy to transfer this discussion to the mailing list. There is information on the "Contribute" page of thespianpy.com about joining the mailing list. Does Actor A...

Great idea! If you had the time to contribute something like that I would definitely be interested.

Hi Andrey, Thanks for the clarification in your scenario. The general behavior of Thespian is that it will re-attempt delivery of a message to an actor once if the actor's...

@todd-cook I think it's reasonable to finally drop Python 2 support, so I have no objections to a migration.

I would also be open to type hints directly in the code, per @mcepl 's comment.

That's convenient, but I'd actually prefer the direct inline annotations and dropping Python 2 support to the `# type: ...` comments described in that pep.

I don't mind multiple questions, although it might get somewhat confusing to have multiple threads of responses, so let us both feel free to split a question into a separate...

Thank you for catching the issue in the director documentation. Just to be sure I didn't miss anything, the main issue was the missing comma between the handlers and filters...