Fetching contributors…
Cannot retrieve contributors at this time
286 lines (205 sloc) 11.5 KB


v1.2.1 (2015-07-20)

v1.2.0 (2013-07-15)

v1.1.0 (2013-01-19)

v1.0.1 (2012-12-12)

v1.0.0 (2012-10-26)

v0.16 (2012-09-19)

  • 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.

v0.15 (2012-08-11)

  • Change the argument of :meth:`pykka.Future.set_exception` from an exception instance to a exc_info three-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`)

v0.14 (2012-04-22)

v0.13 (2011-09-24)

  • 10x speedup of traversible attribute access by reusing proxies.
  • 1.1x speedup of callable attribute access by reusing proxies.

v0.12.4 (2011-07-30)

  • 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_all work 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`)

v0.12.3 (2011-06-25)

v0.12.2 (2011-05-05)

v0.12.1 (2011-04-25)

v0.12 (2011-03-30)

  • 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.