Nameko

Latest version: v2.14.1

Safety actively analyzes 629811 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 11

1.8.0

Not secure
-------------

Released 2014-06-13

* Now passing ``exc_info`` tuples instead of bare exceptions to
``worker_result`` and ``handle_result``, to enable exception processing in
non-worker greenthreads.

1.7.2

Not secure
-------------

Released 2014-06-10

* :meth:`~nameko.containers.ServiceContainer._run_worker` now calls any
``handle_result`` method before dependency teardown.
* Serialization errors now generate a specific error message rather
than bubbling into the container.
* Minor change to ``nameko_doc`` output.

1.7.1

Not secure
-------------

Released 2014-05-20

* Added ``language``, ``auth_token`` and ``user_id`` dependency providers to
make context data available to service workers.
* Refactored constants into their own module.
* Minor test changes to enable testing on shared rabbit brokers.

1.7.0

Not secure
-------------

Released 2014-05-07

* :meth:`~nameko.containers.ServiceContainer.spawn_worker` now throws
:class:`~nameko.exceptions.ContainerBeingKilled` if a ``kill`` is
in progress, since some providers may already be dead. Providers should catch
this and e.g. requeue rpc messages. There is a race condition between
completing the kill sequence and remaining entrypoints firing.

1.6.1

Not secure
-------------

Released 2014-04-03

* Revert changes to legacy exception serialization to maintain backwards
compatibility with old clients.
* Add forwards compatibility for future clients that wish to serialize
exceptions into more data
* Promote conftest rabbit manipulations to test helpers

1.6.0

Not secure
-------------

Released 2014-03-31

* Rename instance_factory to worker_factory
* Raise :class:`~nameko.exception.IncorrectSignature` instead of
``RemoteError: TypeError`` if an RPC method is called with invalid arguments.
* Raise :class:`~nameko.exception.MethodNotFound` instead of
``RemoteError: MethodNotFound`` if a non-existent RPC method is called.
* Let log handlers format warning messages so that aggregators group them
correctly.
* Expose the entire dependency provider (rather than just the method name) to
the worker context.

Page 9 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.