Commit eb1ad664 authored by Alex Willmer's avatar Alex Willmer Committed by David Wilson

docs: Fix out of date get_data() snippets

As of adc8fe3aed470de55a6e5ea3d7c6a31f7c6d1ff1 Receiver objects do not
have a get_data() method and Receiver.get() does not unpickle the
message.
parent 3261c561
...@@ -677,7 +677,9 @@ Context Class ...@@ -677,7 +677,9 @@ Context Class
recv = context.call_async(os.check_output, 'ls /tmp/') recv = context.call_async(os.check_output, 'ls /tmp/')
try: try:
print recv.get_data() # Prints output once it is received. # Prints output once it is received.
msg = recv.get()
print msg.unpickle()
except mitogen.core.CallError, e: except mitogen.core.CallError, e:
print 'Call failed:', str(e) print 'Call failed:', str(e)
......
...@@ -170,11 +170,12 @@ It is a simple wrapper around the more flexible :meth:`Context.call_async`, ...@@ -170,11 +170,12 @@ It is a simple wrapper around the more flexible :meth:`Context.call_async`,
which immediately returns a :class:`Receiver <mitogen.core.Receiver>` wired up which immediately returns a :class:`Receiver <mitogen.core.Receiver>` wired up
to receive the return value instead. A receiver may simply be discarded, kept to receive the return value instead. A receiver may simply be discarded, kept
around indefinitely without ever reading its result, or used to wait on the around indefinitely without ever reading its result, or used to wait on the
results from several calls. Here :meth:`get_data() <mitogen.core.Receiver.get>` results from several calls. Here :meth:`get() <mitogen.core.Receiver.get>`
is called to block the thread until the result arrives:: is called to block the thread until the result arrives::
>>> call = local.call_async(time.time) >>> call = local.call_async(time.time)
>>> print call.get_data() >>> msg = call.get()
>>> print msg.unpickle()
1507292737.75547 1507292737.75547
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment