Warning: chmod(): Operation not permitted in /var/www/hopeinstoughton_www/wp-content/plugins/simple-universal-google-analytics/main.php on line 8 [0] in function chmod in /var/www/hopeinstoughton_www/wp-content/plugins/simple-universal-google-analytics/main.php on line 8 [1] in function include_once in /var/www/hopeinstoughton_www/wp-settings.php on line 560 [2] in function require_once in /var/www/hopeinstoughton_www/wp-config.php on line 85 [3] in function require_once in /var/www/hopeinstoughton_www/wp-load.php on line 50 [4] in function require_once in /var/www/hopeinstoughton_www/wp-blog-header.php on line 13 [5] in function require in /var/www/hopeinstoughton_www/index.php on line 17
| Server IP : 94.177.8.99 / Your IP : 216.73.217.165 Web Server : Apache/2.4.58 (Ubuntu) System : Linux aries 6.8.0-134-generic #134-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 26 18:43:11 UTC 2026 x86_64 User : www-data ( 33) PHP Version : 8.1.34 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /nuitka/eggshell.build/ |
Upload File : |
�� �value�.�� �args�.�K .��2 �builtins��AttributeError���h�
IndexError�����.��
�Future�.�� �_source_traceback�.�).�� J����.�� �__file__�.��
� functools�.�� �wraps�.�� �wrapper�.�� �coroutine.<locals>.wrapper�.�� � __wrapped__�.�� �__tornado_coroutine__�.��E X> Decorator for asynchronous generators.
For compatibility with older versions of Python, coroutines may
also "return" by raising the special exception `Return(value)
<Return>`.
Functions with this decorator return a `.Future`.
.. warning::
When exceptions occur inside a coroutine, the exception
information will be stored in the `.Future` object. You must
examine the result of the `.Future` object, or the exception
may go unnoticed by your code. This means yielding the function
if called from another coroutine, using something like
`.IOLoop.run_sync` for top-level calls, or passing the `.Future`
to `.IOLoop.add_future`.
.. versionchanged:: 6.0
The ``callback`` argument was removed. Use the returned
awaitable object instead.
�.�� �_create_future�.�� � contextvars�.�� � copy_context�.�� �run�.�� �
_fake_ctx_run�.�� �func�.��
�Return�.�� �_value_from_stopiteration�.�� �future_set_exc_info�.�� �sys�.�� �exc_info�.��
� Generator�.�� �next�.��& �"future_set_result_unless_cancelled�.��
�Runner�.��
�future�.�� �yielded�.�� �add_done_callback�.�� �<lambda>�.��0 �,coroutine.<locals>.wrapper.<locals>.<lambda>�.��
�runner�.��� ��Return whether *func* is a coroutine function, i.e. a function
wrapped with `~.gen.coroutine`.
.. versionadded:: 4.5
�.��
� __class__�.�� �__init__�.��- �)You must provide args or kwargs, not both�.�� � _unfinished�.�� � collections�.�� �deque�.��
� _finished�.�� �
current_index�.�� �current_future�.�� �_running_future�.�� �future_add_done_callback�.�� �self�.�� �_done_callback�.��* �&too many values to unpack (expected 2)�.��
� <genexpr>�.��, �(WaitIterator.__init__.<locals>.<genexpr>�.��6 �2Returns True if this iterator has no more results.�.�� �_return_result�.�� �popleft�.��� ��Returns a `.Future` that will yield the next available result.
Note that this `.Future` will not be the same object as any of
the inputs.
�.�� �done�.��
�append�.�� �no future is running�.�� � chain_future�.�� �pop�.��� ��Called set the returned future's state that of the future
we yielded, and set the current future for the iterator.
�.�h.�� �StopAsyncIteration�.�� � multi_future�.�� �quiet_exceptions���.�� X Runs multiple asynchronous operations in parallel.
``children`` may either be a list or a dict whose values are
yieldable objects. ``multi()`` returns a new yieldable
object that resolves to a parallel structure containing their
results. If ``children`` is a list, the result is a list of
results in the same order; if it is a dict, the result is a dict
with the same keys.
That is, ``results = yield multi(list_of_futures)`` is equivalent
to::
results = []
for future in list_of_futures:
results.append(yield future)
If any children raise exceptions, ``multi()`` will raise the first
one. All others will be logged, unless they are of types
contained in the ``quiet_exceptions`` argument.
In a ``yield``-based coroutine, it is not normally necessary to
call this function directly, since the coroutine runner will
do it automatically when a list or dict is yielded. However,
it is necessary in ``await``-based coroutines, or to pass
the ``quiet_exceptions`` argument.
This function is available under the names ``multi()`` and ``Multi()``
for historical reasons.
Cancelling a `.Future` returned by ``multi()`` does not cancel its
children. `asyncio.gather` is similar to ``multi()``, but it does
cancel its children.
.. versionchanged:: 4.2
If multiple yieldables fail, any exceptions after the first
(which is raised) will be logged. Added the ``quiet_exceptions``
argument to suppress this logging for selected exception types.
.. versionchanged:: 4.3
Replaced the class ``Multi`` and the function ``multi_future``
with a unified function ``multi``. Added support for yieldables
other than ``YieldPoint`` and `.Future`.
�.�� �keys�.��
�values�.�� �convert_yielded�.�� �fut�.��
�return�.�� �callback�.��" � multi_future.<locals>.callback�.��
� listening�.�� �add�.��� X� Wait for multiple asynchronous futures in parallel.
Since Tornado 6.0, this function is exactly the same as `multi`.
.. versionadded:: 4.0
.. versionchanged:: 4.2
If multiple ``Futures`` fail, any exceptions after the first (which is
raised) will be logged. Added the ``quiet_exceptions``
argument to suppress this logging for selected exception types.
.. deprecated:: 4.3
Use `multi` instead.
�.��
� is_future�.�� � _NullFuture�.��# � multi_future.<locals>.<genexpr>�.�� �unfinished_children�.��
�remove�.�� �
children_futs�.�� � result_list�.��
�result�.�hD.�� �app_log�.�� �error�.��( �!Multiple exceptions in yield list����.�� h ��.�� �
set_result�.�� X Converts ``x`` into a `.Future`.
If ``x`` is already a `.Future`, it is simply returned; otherwise
it is wrapped in a new `.Future`. This is suitable for use as
``result = yield gen.maybe_future(f())`` when you don't know whether
``f()`` returns a `.Future` or not.
.. deprecated:: 4.3
This function only handles ``Futures``, not other yieldable objects.
Instead of `maybe_future`, check for the non-future result types
you expect (often just ``None``), and ``yield`` anything unknown.
�.��
�IOLoop�.�� �current�.�� �error_callback�.��( �$with_timeout.<locals>.error_callback�.�� }�hKNs.�� �timeout_callback�.��* �&with_timeout.<locals>.timeout_callback�.�� � add_timeout�.��" � with_timeout.<locals>.<lambda>�.�� �
add_future�.��� X� Wraps a `.Future` (or other yieldable object) in a timeout.
Raises `tornado.util.TimeoutError` if the input future does not
complete before ``timeout``, which may be specified in any form
allowed by `.IOLoop.add_timeout` (i.e. a `datetime.timedelta` or
an absolute time relative to `.IOLoop.time`)
If the wrapped `.Future` fails after it has timed out, the exception
will be logged unless it is either of a type contained in
``quiet_exceptions`` (which may be an exception type or a sequence of
types), or an ``asyncio.CancelledError``.
The wrapped `.Future` is not canceled when the timeout expires,
permitting it to be reused. `asyncio.wait_for` is similar to this
function but it does cancel the wrapped `.Future` on timeout.
.. versionadded:: 4.0
.. versionchanged:: 4.1
Added the ``quiet_exceptions`` argument and the logging of unhandled
exceptions.
.. versionchanged:: 4.4
Added support for yieldable objects other than `.Future`.
.. versionchanged:: 6.0.3
``asyncio.CancelledError`` is now always considered "quiet".
.. versionchanged:: 6.2
``tornado.util.TimeoutError`` is now an alias to ``asyncio.TimeoutError``.
�.�� �asyncio�.�� �CancelledError�.��( �$Exception in Future %r after timeout�.�� }�h �s.�� �
set_exception�.�� � TimeoutError�.��
�Timeout���.�� �future_converted�.�� �io_loop�.�� �remove_timeout�.�� �timeout_handle�.�� �
call_later�.�� �sleep.<locals>.<lambda>�.��� X� Return a `.Future` that resolves after the given number of seconds.
When used with ``yield`` in a coroutine, this is a non-blocking
analogue to `time.sleep` (which should not be used in coroutines
because it is blocking)::
yield gen.sleep(0.5)
Note that calling this function on its own does nothing; you must
wait on the `.Future` it returns (usually by yielding it).
.. versionadded:: 4.1
�.�� �f�.�� �ctx_run�.�� �gen�.�� �
result_future�.�� � _null_future�.�� �running�.�� �finished�.�� � handle_yield�.�� �No pending future�.�� �throw�.�� �send�.��o �kStarts or resumes the generator, running until it reaches a
yield point that is not ready.
�.�� �
BadYieldError�.��
�moment�.�� � add_callback�.�� �no pending future�.�� �Any�.�� �inner�.��& �"Runner.handle_yield.<locals>.inner�.�� h�list���h�dict�����.�� �multi�.��
�typing�.�� �cast�.�� � isawaitable�.�� �_wrap_awaitable�.�� �yielded unknown object %r�.��F X? Convert a yielded object into a `.Future`.
The default implementation accepts lists, dictionaries, and
Futures. This has the side effect of starting any coroutines that
did not start themselves, similar to `asyncio.ensure_future`.
If the `~functools.singledispatch` library is available, this function
may be extended to support additional types. For example::
@convert_yielded.register(asyncio.Future)
def _(asyncio_future):
return tornado.platform.asyncio.to_tornado_future(asyncio_future)
.. versionadded:: 4.1
�.��g X` ``tornado.gen`` implements generator-based coroutines.
.. note::
The "decorator and generator" approach in this module is a
precursor to native coroutines (using ``async def`` and ``await``)
which were introduced in Python 3.5. Applications that do not
require compatibility with older versions of Python should use
native coroutines instead. Some parts of this module are still
useful with native coroutines, notably `multi`, `sleep`,
`WaitIterator`, and `with_timeout`. Some of these functions have
counterparts in the `asyncio` module which may be used as well,
although the two may not necessarily be 100% compatible.
Coroutines provide an easier way to work in an asynchronous
environment than chaining callbacks. Code using coroutines is
technically asynchronous, but it is written as a single generator
instead of a collection of separate functions.
For example, here's a coroutine-based handler:
.. testcode::
class GenAsyncHandler(RequestHandler):
@gen.coroutine
def get(self):
http_client = AsyncHTTPClient()
response = yield http_client.fetch("http://example.com")
do_something_with_response(response)
self.render("template.html")
.. testoutput::
:hide:
Asynchronous functions in Tornado return an ``Awaitable`` or `.Future`;
yielding this object returns its result.
You can also yield a list or dict of other yieldable objects, which
will be started at the same time and run in parallel; a list or dict
of results will be returned when they are all finished:
.. testcode::
@gen.coroutine
def get(self):
http_client = AsyncHTTPClient()
response1, response2 = yield [http_client.fetch(url1),
http_client.fetch(url2)]
response_dict = yield dict(response3=http_client.fetch(url3),
response4=http_client.fetch(url4))
response3 = response_dict['response3']
response4 = response_dict['response4']
.. testoutput::
:hide:
If ``tornado.platform.twisted`` is imported, it is also possible to
yield Twisted's ``Deferred`` objects. See the `convert_yielded`
function to extend this mechanism.
.. versionchanged:: 3.2
Dict support added.
.. versionchanged:: 4.1
Support added for yielding ``asyncio`` Futures and Twisted Deferreds
via ``singledispatch``.
�.�� �__doc__�.��9 �5/usr/local/lib/python3.8/dist-packages/tornado/gen.py�.�� �__spec__�.��
�origin�.�� � has_location�.�� �
__cached__�.�� �collections.abc�.�� h ��.�� �concurrent.futures�.�� �
concurrent�.�� �datetime�.�� �singledispatch�.�� �inspect�.�� h���.�� �types�.�� �tornado.concurrent�.�� (hhQh?hh2h t�.�� �tornado.ioloop�.�� h`��.�� � tornado.log�.�� hY��.�� � tornado.util�.�� hp��.�� �Union�.�� �Callable�.�� �List�.�� �Type�.�� �Tuple�.��
� Awaitable�.�� �Dict�.�� �overload�.�� �TypeVar�.�� �_T���.�� �_T�.�� �futures�.�� �
_Yieldable�.�� h� Exception�����.��
� metaclass�.�� � __prepare__�.�� �
KeyReuseError�.�� � __getitem__�.��2 �.%s.__prepare__() must return a mapping, not %s�.�� �__name__�.�� � <metaclass>�.�� � tornado.gen�.�� �
__module__�.�� � __qualname__�.�� �__orig_bases__�.�� �UnknownKeyError�.�� �LeakedCallbackError�.�� �ReturnValueIgnoredError�.�� �e�.�� h�
StopIteration����Return���.�� �kw�.��j � nuitka.constants.Serialization��BuiltinSpecialValue���)��}�h �Ellipsis�sb�Generator[Any, Any, _T]���.�� h�)��}�h h�sb�
Future[_T]���.��
� coroutine�.�� �is_coroutine_function�.��� X� Special exception to return a value from a `coroutine`.
If this exception is raised, its value argument is used as the
result of the coroutine::
@gen.coroutine
def fetch_json(url):
response = yield AsyncHTTPClient().fetch(url)
raise gen.Return(json_decode(response.body))
In Python 3.3, this exception is no longer necessary: the ``return``
statement can be used directly to return a value (previously
``yield`` and ``return`` with a value could not be combined in the
same function).
By analogy with the return statement, the value argument is optional,
but it is never necessary to ``raise gen.Return()``. The ``return``
statement can be used with no arguments instead.
�.�� N��.�� �Return.__init__�.�� h�object�����.�� � WaitIterator�.��� X� Provides an iterator to yield the results of awaitables as they finish.
Yielding a set of awaitables like this:
``results = yield [awaitable1, awaitable2]``
pauses the coroutine until both ``awaitable1`` and ``awaitable2``
return, and then restarts the coroutine with the results of both
awaitables. If either awaitable raises an exception, the
expression will raise that exception and all the results will be
lost.
If you need to get the result of each awaitable as soon as possible,
or if you need the result of some awaitables even if others produce
errors, you can use ``WaitIterator``::
wait_iterator = gen.WaitIterator(awaitable1, awaitable2)
while not wait_iterator.done():
try:
result = yield wait_iterator.next()
except Exception as e:
print("Error {} from {}".format(e, wait_iterator.current_future))
else:
print("Result {} received from {} at {}".format(
result, wait_iterator.current_future,
wait_iterator.current_index))
Because results are returned as soon as they are available the
output from the iterator *will not be in the same order as the
input arguments*. If you need to know which future produced the
current result, you can use the attributes
``WaitIterator.current_future``, or ``WaitIterator.current_index``
to get the index of the awaitable from the input list. (if keyword
arguments were used in the construction of the `WaitIterator`,
``current_index`` will use the corresponding keyword).
On Python 3.5, `WaitIterator` implements the async iterator
protocol, so it can be used with the ``async for`` statement (note
that in this version the entire iteration is aborted if any value
raises an exception, while the previous example can continue past
individual errors)::
async for result in gen.WaitIterator(future1, future2):
print("Result {} received from {} at {}".format(
result, wait_iterator.current_future,
wait_iterator.current_index))
.. versionadded:: 4.1
.. versionchanged:: 4.3
Added ``async for`` support in Python 3.5.
�.��
�kwargs�.�� �WaitIterator.__init__�.�� �bool�.�� �WaitIterator.done�.�� �WaitIterator.next�.�� �WaitIterator._done_callback�.�� �WaitIterator._return_result�.�� �
AsyncIterator�.��
� __aiter__�.�� �WaitIterator.__aiter__�.��
� __anext__�.�� �WaitIterator.__anext__�.�� )��.�� �children�.��7 �3Union[Type[Exception], Tuple[Type[Exception], ...]]�.��% �!Union[Future[List], Future[Dict]]�.�� �Multi�.�� �x�.�� � maybe_future�.�� �timeout�.��
� timedelta�.�� � with_timeout�.��- }�(�duration�h�float���hK� Future[None]�u.�� �sleep�.��� X� _NullFuture resembles a Future that finished with a result of None.
It's not actually a `Future` to avoid depending on a particular event loop.
Handled as a special case in the coroutine runner.
We lie and tell the type checker that a _NullFuture is a Future so
we don't have to leak _NullFuture into lots of public APIs. But
this means that the type checker can't warn us when we're passing
a _NullFuture into a code path that doesn't understand what to do
with it.
�.�� �_NullFuture.result�.�� �_NullFuture.done�.��� X� A special object which may be yielded to allow the IOLoop to run for
one iteration.
This is not needed in normal use but it can be helpful in long-running
coroutines that are likely to yield Futures that are ready instantly.
Usage: ``yield gen.moment``
In native coroutines, the equivalent of ``yield gen.moment`` is
``await asyncio.sleep(0)``.
.. versionadded:: 4.0
.. deprecated:: 4.5
``yield None`` (or ``yield`` with no argument) is now equivalent to
``yield gen.moment``.
�.��� ��Internal implementation of `tornado.gen.coroutine`.
Maintains information about pending callbacks and their results.
The results of the generator are stored in ``result_future`` (a
`.Future`)
�.��" � Generator[_Yieldable, Any, _T]�.�� �
Future[_T]�.�� �
first_yielded�.�� �Runner.__init__�.�� �
Runner.run�.�� �Runner.handle_yield�.�� �typ�.��
� Exception�.�� �tb�.�� �
TracebackType�.�� �handle_exception�.�� �Runner.handle_exception�.�� �
ensure_future�.�� �async�.�� �.0��i���.�� j j hz��.�� j �k�hz��.�� �_�h&��.�� h&��.�� hz��.�� h!hthv��.�� hthv��.�� �<module tornado.gen>�.�� h(��.�� h3��.�� (h3hh�h�h!t�.�� (h3h{h|h}j t�.�� h3h h(��.��# h!�source_traceback��filename���.�� h3h<��.�� hzhhՇ�.��
h3h<�res���.�� hЅ�.�� (hJhWhzh�hThVh!hDhGt�.�� (hVh!hGhDhTt�.�� h"��.�� h��.�� hh
��.�� h!h�hD��.�� (h3j h j t�.�� h3h"h���.�� hzh3��.�� h�hJ��.�� h�hD��.��% (h�hDhG� children_seq�hVhTh!hLhNhzt�.�� (h3h!h h h"h�t�.��
j hz��.�� hXhshb��.�� hbhshX��.�� (h�h!hDhshXhthbhehvt�.�� (hh�h!h{hXh�h"h&ht�.�� � �.