o US`cI@sdddlmZddlZddZddZddZd d Zd d ZGd ddeZ eddZ ddZ dS))contextmanagerNcCs tj|dS)zUse as a context manager to create a cancel scope with the given absolute deadline. Args: deadline (float): The deadline. deadline)trioZ CancelScoperr9/usr/local/lib/python3.10/dist-packages/trio/_timeouts.py move_on_ats rcC |dkrtdtt|S)zUse as a context manager to create a cancel scope whose deadline is set to now + *seconds*. Args: seconds (float): The timeout. Raises: ValueError: if timeout is less than zero. rtimeout must be non-negative) ValueErrorrr current_timesecondsrrr move_on_afters rcstjddIdHdS)z}Pause execution of the current task forever (or until cancelled). Equivalent to calling ``await sleep(math.inf)``. cSs tjjjS)N)rlowlevelZAbortZ SUCCEEDED)_rrr(s zsleep_forever..N)rrZwait_task_rescheduledrrrr sleep_forever"srcs<t|tIdHWddS1swYdS)aPause execution of the current task until the given time. The difference between :func:`sleep` and :func:`sleep_until` is that the former takes a relative time and the latter takes an absolute time according to Trio's internal clock (as returned by :func:`current_time`). Args: deadline (float): The time at which we should wake up again. May be in the past, in which case this function executes a checkpoint but does not block. N)rrrrrr sleep_until+s "rcsH|dkr td|dkrtjIdHdStt|IdHdS)aPause execution of the current task for the given number of seconds. Args: seconds (float): The number of seconds to sleep. May be zero to insert a checkpoint without actually blocking. Raises: ValueError: if *seconds* is negative. rzduration must be non-negativeN)r rr checkpointrr r rrrsleep<s  rc@seZdZdZdS) TooSlowErrorzRRaised by :func:`fail_after` and :func:`fail_at` if the timeout expires. N)__name__ __module__ __qualname____doc__rrrrrOsrccs>t| }|VWdn1swY|jrtdS)aCreates a cancel scope with the given deadline, and raises an error if it is actually cancelled. This function and :func:`move_on_at` are similar in that both create a cancel scope with a given absolute deadline, and if the deadline expires then both will cause :exc:`Cancelled` to be raised within the scope. The difference is that when the :exc:`Cancelled` exception reaches :func:`move_on_at`, it's caught and discarded. When it reaches :func:`fail_at`, then it's caught and :exc:`TooSlowError` is raised in its place. Raises: TooSlowError: if a :exc:`Cancelled` exception is raised in this scope and caught by the context manager. N)rZcancelled_caughtr)rscoperrrfail_atVs rcCr )aCreates a cancel scope with the given timeout, and raises an error if it is actually cancelled. This function and :func:`move_on_after` are similar in that both create a cancel scope with a given timeout, and if the timeout expires then both will cause :exc:`Cancelled` to be raised within the scope. The difference is that when the :exc:`Cancelled` exception reaches :func:`move_on_after`, it's caught and discarded. When it reaches :func:`fail_after`, then it's caught and :exc:`TooSlowError` is raised in its place. Raises: TooSlowError: if a :exc:`Cancelled` exception is raised in this scope and caught by the context manager. ValueError: if *seconds* is less than zero. rr )r rrr r rrr fail_afterosr) contextlibrrrrrrr Exceptionrrrrrrrs