Stein Magnus Jodal

Without looking at the code, I find this interesting as a use case for what should be possible to do without altering Pykka itself. Setting this to milestone v2.0 to...

Thanks for providing a good howto on how to implement a supervision pattern yourself. Supervision is mostly lacking from Pykka because of time/effort/need, and not because I oppose it. I'm...

Thanks for the tip! We now have the `Envelope` wrapper around messages, so adding extra metadata like a `sender` attribute is now straight forward. The open question is how to...

If you leave out any considerations about having actors running on different executors talking to each other, e.g. a system with only multiprocessing actors, you basically just need: - something...

I don't know of that many projects using Pykka, but at least in Mopidy we usually keep quite strictly to the actor rules. That said, I think that you'll have...

The default implementation of `on_receive()` in the `Actor` class will log any unexpected messages on the `WARNING` log level. If using that, your example could then be updated to: ```...

Something like this should work: ``` python import time import pykka class StringPrinter(pykka.ThreadingActor): def on_receive(self, message): print 'I got a message:', message class StringProducer(pykka.ThreadingActor): def __init__(self, target, string): super(StringProducer, self).__init__()...

I haven't used much HTTP libs, so I don't off hand know of any async HTTP libs for Python. Ignoring async/sync, I'd have a look at `requests`.

Ref. http://www.pykka.org/en/latest/#what-pykka-is-not, Pykka doesn't currently have a supervisor hierarchy, which is a precursor for stopping children when the parent is stopped. I'm open to adding this in the future.

Using Ubuntu 18.10 and udev 239-7ubuntu10.4, I can confirm that `--reload` is the documented option, and that `--reload-rules` yields no output, just like `--reload`. However, it seems like the system...