From eb1ad66469f6dfa914e8ebd5a953815ab13bff92 Mon Sep 17 00:00:00 2001 From: Alex Willmer Date: Wed, 14 Feb 2018 23:28:53 +0000 Subject: [PATCH] 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. --- docs/api.rst | 4 +++- docs/getting_started.rst | 5 +++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/api.rst b/docs/api.rst index 615052a3..b6c68354 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -677,7 +677,9 @@ Context Class recv = context.call_async(os.check_output, 'ls /tmp/') 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: print 'Call failed:', str(e) diff --git a/docs/getting_started.rst b/docs/getting_started.rst index 23008f55..65f89ae9 100644 --- a/docs/getting_started.rst +++ b/docs/getting_started.rst @@ -170,11 +170,12 @@ It is a simple wrapper around the more flexible :meth:`Context.call_async`, which immediately returns a :class:`Receiver ` wired up 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 -results from several calls. Here :meth:`get_data() ` +results from several calls. Here :meth:`get() ` is called to block the thread until the result arrives:: >>> call = local.call_async(time.time) - >>> print call.get_data() + >>> msg = call.get() + >>> print msg.unpickle() 1507292737.75547