- Increase log level of :func:`pykka.debug.log_thread_tracebacks` debugging helper from :attr:`logging.INFO` to :attr:`logging.CRITICAL`.
- Fix errors in docs examples. (PR: :issue:`29`, :issue:`43`)
- Fix typos in docs.
- Various project setup and development improvements.
Enforce that multiple calls to :meth:`pykka.Future.set` raises an exception. This was already the case for some implementations. The exception raised is not specified.
Add :meth:`~Pykka.Future.filter`, :meth:`~pykka.Future.join`, :meth:`~pykka.Future.map`, and :meth:`~pykka.Future.reduce` as convenience methods using the new :meth:`~pykka.Future.set_get_hook` method.
Add support for running actors based on eventlet greenlets. See :mod:`pykka.eventlet` for details. Thanks to Jakub Stasiak for the implementation.
Update documentation to reflect that the
reply_tofield on the message is private to Pykka. Actors should reply to messages simply by returning the response from :meth:`~pykka.Actor.on_receive`. The internal field is renamed to
pykka_reply_toa to avoid collisions with other message fields. It is also removed from the message before the message is passed to :meth:`~pykka.Actor.on_receive`. Thanks to Jakub Stasiak.
When messages are left in the actor inbox after the actor is stopped, those messages that are expecting a reply is now rejected by replying with an :exc:`~pykka.ActorDeadError` exception. This causes other actors blocking on the returned :class:`~pykka.Future` without a timeout to raise the exception instead of waiting forever. Thanks to Jakub Stasiak.
This makes the behavior of messaging an actor around the time it is stopped more consistent:
- Messaging an already dead actor immediately raises :exc:`~pykka.ActorDeadError`.
- Messaging an alive actor that is stopped before it processes the message will cause the reply future to raise :exc:`~pykka.ActorDeadError`.
Similarly, if you ask an actor to stop multiple times, and block on the responses, all the messages will now get an reply. Previously only the first message got a reply, potentially making the application wait forever on replies to the subsequent stop messages.
When :meth:`~pykka.ActorRef.ask` is used to asynchronously message a dead actor (e.g.
blockset to :class:`False`), it will no longer immediately raise :exc:`~pykka.ActorDeadError`. Instead, it will return a future and fail the future with the :exc:`~pykka.ActorDeadError` exception. This makes the interface more consistent, as you'll have one instead of two ways the call can raise exceptions under normal conditions. If :meth:`~pykka.ActorRef.ask` is called synchronously (e.g.
blockset to :class:`True`), the behavior is unchanged.
A change to :meth:`~pykka.ActorRef.stop` reduces the likelyhood of a race condition when asking an actor to stop multiple times by not checking if the actor is dead before asking it to stop, but instead just go ahead and leave it to :meth:`~pykka.ActorRef.tell` to do the alive-or-dead check a single time, and as late as possible.
Change :meth:`~pykka.ActorRef.is_alive` to check the actor's runnable flag instead of checking if the actor is registrered in the actor registry.
- An exception raised in :meth:`pykka.Actor.on_start` didn't stop the actor properly. Thanks to Jay Camp for finding and fixing the bug.
- Make sure exceptions in :meth:`pykka.Actor.on_stop` and :meth:`pykka.Actor.on_failure` is logged.
- Add :attr:`pykka.ThreadingActor.use_daemon_thread` flag for optionally running an actor on a daemon thread, so that it doesn't block the Python program from exiting. (Fixes: :issue:`14`)
- Add :func:`pykka.debug.log_thread_tracebacks` debugging helper. (Fixes: :issue:`17`)
- Name the threads of :class:`pykka.ThreadingActor` after the actor class name instead of "PykkaThreadingActor-N" to ease debugging. (Fixes: :issue:`12`)
Backwards incompatible: Removed :meth:`pykka.ActorRef.send_one_way` and :meth:`pykka.ActorRef.send_request_reply`, which have been deprecated since v0.14. Use :meth:`pykka.ActorRef.tell` and :meth:`pykka.ActorRef.ask` instead.
This is backwards incompatible because you no longer have access to fields/methods of the thread/greenlet that runs the actor through fields/methods on the actor itself. This was never advertised in Pykka's docs or examples, but the fields/methods have always been available.
As a positive side effect, this fixes an issue on Python 3.x, that was introduced in Pykka 0.16, where :class:`pykka.ThreadingActor` would accidentally override the method :meth:`threading.Thread._stop`.
Backwards incompatible: Actors that override :meth:`__init__() <pykka.Actor.__init__>` must call the method they override. If not, the actor will no longer be properly initialized. Valid ways to call the overridden :meth:`__init__` method include:
super(MyActorSubclass, self).__init__() # or pykka.ThreadingActor.__init__() # or pykka.gevent.GeventActor.__init__()
super(MyActorSubclass, self).__init__(1, 2, 3, foo='bar')
Allow all public classes and functions to be imported directly from the :mod:`pykka` module. E.g.
from pykka.actor import ThreadingActorcan now be written as
from pykka import ThreadingActor. The exception is :mod:`pykka.gevent`, which still needs to be imported from its own package due to its additional dependency on gevent.
- Let actors access themselves through a proxy. See the :class:`pykka.ActorProxy` documentation for use cases and usage examples. (Fixes: :issue:`9`)
- Give proxies direct access to the actor instances for inspecting available attributes. This access is only used for reading, and works since both threading and gevent based actors share memory with other actors. This reduces the creation cost for proxies, which is mostly visible in test suites that are starting and stopping lots of actors. For the Mopidy test suite the run time was reduced by about 33%. This change also makes self-proxying possible.
- Fix bug where :meth:`pykka.Actor.stop` called by an actor on itself did not process the remaining messages in the inbox before the actor stopped. The behavior now matches the documentation.
- Change the argument of :meth:`pykka.Future.set_exception` from an exception
instance to a
exc_infothree-tuple. Passing just an exception instance to the method still works, but it is deprecated and may be unsupported in a future release.
- Due to the above change, :meth:`pykka.Future.get` will now reraise exceptions with complete traceback from the point when the exception was first raised, and not just a traceback from when it was reraised by :meth:`get`. (Fixes: :issue:`10`)
- Add :attr:`pykka.__version__` to conform with PEP 396. This deprecates :attr:`pykka.VERSION` and :meth:`pykka.get_version`.
- Add :meth:`pykka.ActorRef.tell` method in favor of now deprecated :meth:`pykka.ActorRef.send_one_way`.
- Add :meth:`pykka.ActorRef.ask` method in favor of now deprecated :meth:`pykka.ActorRef.send_request_reply`.
- :class:`ThreadingFuture.set() <pykka.ThreadingFuture>` no longer makes a copy of the object set on the future. The setter is urged to either only pass immutable objects through futures or copy the object himself before setting it on the future. This is a less safe default, but it removes unecessary overhead in speed and memory usage for users of immutable data structures. For example, the Mopidy test suite of about 1000 tests, many which are using Pykka, is still passing after this change, but the test suite runs approximately 20% faster.
- 10x speedup of traversible attribute access by reusing proxies.
- 1.1x speedup of callable attribute access by reusing proxies.
- Change and document order in which :meth:`pykka.ActorRegistry.stop_all` stops
actors. The new order is the reverse of the order the actors were started in.
This should make
stop_allwork for programs with simple dependency graphs in between the actors. For applications with more complex dependency graphs, the developer still needs to pay attention to the shutdown sequence. (Fixes: :issue:`8`)
- If an actor that was stopped from :meth:`pykka.Actor.on_start`, it would unregister properly, but start the receive loop and forever block on receiving incoming messages that would never arrive. This left the thread alive and isolated, ultimately blocking clean shutdown of the program. The fix ensures that the receive loop is never executed if the actor is stopped before the receive loop is started.
- Set the thread name of any :class:`pykka.ThreadingActor` to
PykkaActorThread-Ninstead of the default
Thread-N. This eases debugging by clearly labeling actor threads in e.g. the output of :func:`threading.enumerate`.
- Add utility method :meth:`pykka.ActorRegistry.broadcast` which broadcasts a message to all registered actors or to a given class of registred actors. (Fixes: :issue:`7`)
- Allow multiple calls to :meth:`pykka.ActorRegistry.unregister` with the same :class:`pykka.actor.ActorRef` as argument without throwing a :exc:`ValueError`. (Fixes: :issue:`5`)
- Make the :class:`pykka.ActorProxy`'s reference to its :class:`pykka.ActorRef`
public as :attr:`pykka.ActorProxy.actor_ref`. The
ActorRefinstance was already exposed as a public field by the actor itself using the same name, but making it public directly on the proxy makes it possible to do e.g.
proxy.actor_ref.is_alive()without waiting for a potentially dead actor to return an
ActorRefinstance you can use. (Fixes: :issue:`3`)
- Actors are now registered in :class:`pykka.registry.ActorRegistry` before they are started. This fixes a race condition where an actor tried to stop and unregister itself before it was registered, causing an exception in :meth:`ActorRegistry.unregister`.
- Stop all running actors on :exc:`BaseException` instead of just
:exc:`KeyboardInterrupt`, so that
- First stable release, as Pykka now is used by the Mopidy project. From now on, a changelog will be maintained and we will strive for backwards compatability.