Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/celery/__pycache__/schedules.cpython-39.pyc
Ðазад
a t�h} � @ sp d Z ddlmZ ddlZddlmZmZ ddlmZ ddlm Z ddl m Z m Z m Z ddl mZmZmZmZ dd lmZ dd lmZ d d lmZ d d lmZ d dlmZm Z m Z m Z m Z m Z m!Z!m"Z" dZ#edd�Z$dZ%dZ&dZ'dZ(dZ)dZ*ddd�dd�Z+G d d � d e,�Z-G d d � d �Z.G d d!� d!e.�Z/G d"d#� d#�Z0G d$d%� d%e.�Z1d0d'd(d)d*d+�d,d-�Z2G d.d/� d/e.�Z3dS )1z;Schedules define the intervals at which periodic tasks run.� )� annotationsN)�bisect� bisect_left)� namedtuple)�Iterable)�datetime� timedelta�tzinfo)�Any�Callable�Mapping�Sequence)�cached_property)�Celery� )� current_app)� AttributeDict)�ffwd�humanize_seconds�localize�maybe_make_aware�maybe_timedelta� remaining�timezone�weekday)�ParseException�schedule�crontab�crontab_parser�maybe_schedule�solar� schedstate��is_due�nextzJInvalid crontab pattern. Valid range is {min}-{max}. '{value}' was found.zoArgument cronspec needs to be of any of the following types: int, str, or an iterable type. {type!r} was given.z}<crontab: {0._orig_minute} {0._orig_hour} {0._orig_day_of_month} {0._orig_month_of_year} {0._orig_day_of_week} (m/h/dM/MY/d)>z?Argument latitude {lat} is invalid, must be between -90 and 90.zBArgument longitude {lon} is invalid, must be between -180 and 180.zAArgument event "{event}" is invalid, must be one of {all_events}.�str��s�returnc C s | d u r dS | S )N�*� )r' r* r* ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/celery/schedules.py� cronfield7 s r, c @ s e Zd ZdZdS )r zARaised by :class:`crontab_parser` when the input can't be parsed.N)�__name__� __module__� __qualname__�__doc__r* r* r* r+ r ; s r c @ s� e Zd Zd)ddd�dd�Zdd�d d �Zdd d �d d�Zddd �dd�Zd*dddd�dd�Zedd�dd��Z e j ddd�d d��Z e d d�d d ��Z e dd�d d!��Z ddd"�d#d$�Zd%dd&�d'd(�ZdS )+� BaseScheduleN�Callable | None� Celery | None��nowfun�appc C s || _ || _d S �N)r5 �_app)�selfr5 r6 r* r* r+ �__init__A s zBaseSchedule.__init__r �r( c C s | j p | jj� S r7 )r5 r6 �now�r9 r* r* r+ r< E s zBaseSchedule.nowr �� last_run_atr( c C s t � �d S r7 ��NotImplementedError�r9 r? r* r* r+ �remaining_estimateH s z BaseSchedule.remaining_estimate�tuple[bool, datetime]c C s t � �d S r7 r@ rB r* r* r+ r# K s zBaseSchedule.is_dueT�bool)�dt� naive_as_utcr( c C s t || j|d�S )N�rG )r �tz)r9 rF rG r* r* r+ r N s z BaseSchedule.maybe_make_awarer c C s | j p t�� S r7 )r8 r Z_get_current_objectr= r* r* r+ r6 R s zBaseSchedule.app�None)r6 r( c C s || _ d S r7 )r8 )r9 r6 r* r* r+ r6 V s r c C s | j jS r7 )r6 r r= r* r* r+ rI Z s zBaseSchedule.tzc C s | j jjS r7 )r6 �confZ enable_utcr= r* r* r+ � utc_enabled^ s zBaseSchedule.utc_enabled)rF r( c C s | j st�|�S |S r7 )rL r Zto_local_fallback)r9 rF r* r* r+ �to_localb s zBaseSchedule.to_localr ��otherr( c C s t |t�r|j| jkS tS r7 )� isinstancer1 r5 �NotImplemented�r9 rO r* r* r+ �__eq__g s zBaseSchedule.__eq__)NN)T)r- r. r/ r: r< rC r# r �propertyr6 �setterr rI rL rM rS r* r* r* r+ r1 ? s �r1 c s� e Zd ZU dZdZded< d%ddddd d �� fd d � Zd dd�dd�Zd dd�dd�Zdd�dd�Z ddd�dd �Z d d�d d �Z e d d�d!d"��Z e dd�d#d$��Z� ZS )&r a� Schedule for periodic task. Arguments: run_every (float, ~datetime.timedelta): Time interval. relative (bool): If set to True the run time will be rounded to the resolution of the interval. nowfun (Callable): Function returning the current date and time (:class:`~datetime.datetime`). app (Celery): Celery app instance. FrE �relativeNzfloat | timedelta | Noner2 r3 rJ )� run_everyrV r5 r6 r( c s$ t |�| _|| _t� j||d� d S )Nr4 )r rW rV �superr: )r9 rW rV r5 r6 �� __class__r* r+ r: { s zschedule.__init__r r r> c C s" t | �|�| j| �| �� �| j�S r7 )r r rW r< rV rB r* r* r+ rC � s �zschedule.remaining_estimaterD c C sD | � |�}| �|�}t|�� d�}|dkr8td| jd�S td|d�S )aG Return tuple of ``(is_due, next_time_to_check)``. Notes: - next time to check is in seconds. - ``(True, 20)``, means the task should be run now, and the next time to check is in 20 seconds. - ``(False, 12.3)``, means the task is not due, but that the scheduler should check again in 12.3 seconds. The next time to check is used to save energy/CPU cycles, it does not need to be accurate but will influence the precision of your schedule. You must also keep in mind the value of :setting:`beat_max_loop_interval`, that decides the maximum number of seconds the scheduler can sleep between re-checking the periodic task intervals. So if you have a task that changes schedule at run-time then your next_run_at check will decide how long it will take before a change to the schedule takes effect. The max loop interval takes precedence over the next check at value returned. .. admonition:: Scheduler max interval variance The default max loop interval may vary for different schedulers. For the default scheduler the value is 5 minutes, but for example the :pypi:`django-celery-beat` database scheduler the value is 5 seconds. r Tr" F)r rC �max� total_secondsr! �seconds)r9 r? � rem_deltaZ remaining_sr* r* r+ r# � s zschedule.is_duer% r; c C s d| j � d�S )Nz<freq: �>)� human_secondsr= r* r* r+ �__repr__� s zschedule.__repr__r rN c C s t |t�r| j|jkS | j|kS r7 )rP r rW rR r* r* r+ rS � s zschedule.__eq__z4tuple[type, tuple[timedelta, bool, Callable | None]]c C s | j | j| j| jffS r7 )rZ rW rV r5 r= r* r* r+ � __reduce__� s zschedule.__reduce__� int | floatc C s t | j�� d�S )Nr )r[ rW r\ r= r* r* r+ r] � s zschedule.secondsc C s t | j�S r7 )r r] r= r* r* r+ r` � s zschedule.human_seconds)NFNN)r- r. r/ r0 rV �__annotations__r: rC r# ra rS rb rT r] r` � __classcell__r* r* rY r+ r m s � %r c @ s� e Zd ZdZeZdZdZdZd$ddd�d d �Zd d d �dd�Z d dd�dd�Z ddd�dd�Z ddd�dd�Z ddd�dd�Z d dd �d d �Zd dd �d!d"�Zd#S )%r a� Parser for Crontab expressions. Any expression of the form 'groups' (see BNF grammar below) is accepted and expanded to a set of numbers. These numbers represent the units of time that the Crontab needs to run on: .. code-block:: bnf digit :: '0'..'9' dow :: 'a'..'z' number :: digit+ | dow+ steps :: number range :: number ( '-' number ) ? numspec :: '*' | range expr :: numspec ( '/' steps ) ? groups :: expr ( ',' expr ) * The parser is a general purpose one, useful for parsing hours, minutes and day of week expressions. Example usage: .. code-block:: pycon >>> minutes = crontab_parser(60).parse('*/15') [0, 15, 30, 45] >>> hours = crontab_parser(24).parse('*/4') [0, 4, 8, 12, 16, 20] >>> day_of_week = crontab_parser(7).parse('*') [0, 1, 2, 3, 4, 5, 6] It can also parse day of month and month of year expressions if initialized with a minimum of 1. Example usage: .. code-block:: pycon >>> days_of_month = crontab_parser(31, 1).parse('*/3') [1, 4, 7, 10, 13, 16, 19, 22, 25, 28, 31] >>> months_of_year = crontab_parser(12, 1).parse('*/2') [1, 3, 5, 7, 9, 11] >>> months_of_year = crontab_parser(12, 1).parse('2-12/2') [2, 4, 6, 8, 10, 12] The maximum possible expanded value returned is found by the formula: :math:`max_ + min_ - 1` z (\w+?)-(\w+)z/(\w+)?z\*�< r �int)�max_�min_c C sj || _ || _t�| j| j �| jft�| j�| jft�| j| j �| j ft�d| j d �| j ff| _ d S )N�^�$) rh ri �re�compile�_range�_steps� _range_steps� _expand_range�_star� _star_steps� _expand_star�pats)r9 rh ri r* r* r+ r: � s �zcrontab_parser.__init__r% zset[int])�specr( c C s: t � }|�d�D ]$}|s"| �d��|t | �|��O }q|S )N�,z empty part)�set�splitr � _parse_part)r9 rv �acc�partr* r* r+ �parse s zcrontab_parser.parsez list[int])r| r( c C s: | j D ]&\}}|�|�}|r||�� � S q| �|f�S r7 )ru �match�groupsrq )r9 r| �regex�handler�mr* r* r+ rz s zcrontab_parser._parse_partz Sequence[str])�toksr( c C sr | � |d �}t|�dkrl| � |d �}||k rZtt|| j| j ��tt| j|d �� S tt||d ��S |gS )Nr r )�_expand_number�len�list�rangeri rh )r9 r� �fr�tor* r* r+ rq s �z crontab_parser._expand_rangec C sB t |�dks|d s | �d��| �|d d� �d d t|d �� S )N� � � empty filter)r� r rq rg �r9 r� r* r* r+ rp s zcrontab_parser._range_stepsc C s0 |r |d s| � d��| �� d d t|d �� S )Nr r� )r rt rg r� r* r* r+ rs s zcrontab_parser._star_stepsr )�argsr( c G s t t| j| j| j ��S r7 )r� r� ri rh )r9 r� r* r* r+ rt % s zcrontab_parser._expand_starr& c C s� t |t�r |d dkr | �d��z t|�}W nB tyn z t|�}W n" tyh td|�d���Y n0 Y n0 | j| j d }||kr�td|� d|� d���|| jk r�td |� d | j� d���|S ) Nr �-z negative numbers not supportedzInvalid weekday literal �.r zInvalid end range: z > zInvalid beginning range: z < ) rP r% r rg � ValueErrorr �KeyErrorri rh )r9 r' �iZmax_valr* r* r+ r� ( s& � �z crontab_parser._expand_numberN)rf r )r- r. r/ r0 r rn ro rr r: r} rz rq rp rs rt r� r* r* r* r+ r � s / r c s� e Zd ZdZd2dddddddd�� fdd� Zed3d d d d d �dd��Zdd d dd�dd�Zdd�dd�Zdd�dd�Z ddd �� fd d � Z d e fdd d!d"d#�d$d%�Z e fdd!d&d'�d(d)�Z dd*d+�d,d-�Zdd.d/�� fd0d1� Z� ZS )4r a� Crontab schedule. A Crontab can be used as the ``run_every`` value of a periodic task entry to add :manpage:`crontab(5)`-like scheduling. Like a :manpage:`cron(5)`-job, you can specify units of time of when you'd like the task to execute. It's a reasonably complete implementation of :command:`cron`'s features, so it should provide a fair degree of scheduling needs. You can specify a minute, an hour, a day of the week, a day of the month, and/or a month in the year in any of the following formats: .. attribute:: minute - A (list of) integers from 0-59 that represent the minutes of an hour of when execution should occur; or - A string representing a Crontab pattern. This may get pretty advanced, like ``minute='*/15'`` (for every quarter) or ``minute='1,13,30-45,50-59/2'``. .. attribute:: hour - A (list of) integers from 0-23 that represent the hours of a day of when execution should occur; or - A string representing a Crontab pattern. This may get pretty advanced, like ``hour='*/3'`` (for every three hours) or ``hour='0,8-17/2'`` (at midnight, and every two hours during office hours). .. attribute:: day_of_week - A (list of) integers from 0-6, where Sunday = 0 and Saturday = 6, that represent the days of a week that execution should occur. - A string representing a Crontab pattern. This may get pretty advanced, like ``day_of_week='mon-fri'`` (for weekdays only). (Beware that ``day_of_week='*/2'`` does not literally mean 'every two days', but 'every day that is divisible by two'!) .. attribute:: day_of_month - A (list of) integers from 1-31 that represents the days of the month that execution should occur. - A string representing a Crontab pattern. This may get pretty advanced, such as ``day_of_month='2-30/2'`` (for every even numbered day) or ``day_of_month='1-7,15-21'`` (for the first and third weeks of the month). .. attribute:: month_of_year - A (list of) integers from 1-12 that represents the months of the year during which execution can occur. - A string representing a Crontab pattern. This may get pretty advanced, such as ``month_of_year='*/3'`` (for the first month of every quarter) or ``month_of_year='2-12/2'`` (for every even numbered month). .. attribute:: nowfun Function returning the current date and time (:class:`~datetime.datetime`). .. attribute:: app The Celery app instance. It's important to realize that any day on which execution should occur must be represented by entries in all three of the day and month attributes. For example, if ``day_of_week`` is 0 and ``day_of_month`` is every seventh day, only months that begin on Sunday and are also in the ``month_of_year`` attribute will have execution events. Or, ``day_of_week`` is 1 and ``day_of_month`` is '1-7,15-21' means every first and third Monday of every month present in ``month_of_year``. r) r% r rJ )�minute�hour� day_of_week� day_of_month� month_of_year�kwargsr( c s� t |�| _t |�| _t |�| _t |�| _t |�| _|| _| �|d�| _| �|d�| _ | �|d�| _ | �|dd�| _ | �|dd�| _ t � jf i |�� d S )N� rf � � r � )r, � _orig_minute� _orig_hour�_orig_day_of_week�_orig_day_of_month�_orig_month_of_year� _orig_kwargs�_expand_cronspecr� r� r� r� r� rX r: )r9 r� r� r� r� r� r� rY r* r+ r: � s zcrontab.__init__r zint | str | Iterablerg zset[Any])�cronspecrh ri r( c C s� t | t�r| h}nTt | t�r.t||��| �}n8t | t�r>| }n(t | t�rRt| �}nttj t | �d���|D ]4}||| ks�||k rjt t j ||d | |d���qj|S )a Expand cron specification. Takes the given cronspec argument in one of the forms: .. code-block:: text int (like 7) str (like '3-5,*/15', '*', or 'monday') set (like {0,15,30,45} list (like [8-17]) And convert it to an (expanded) set representing all time unit values on which the Crontab triggers. Only in case of the base type being :class:`str`, parsing occurs. (It's fast and happens only once for each Crontab instance, so there's no significant performance overhead involved.) For the other base types, merely Python type conversions happen. The argument ``max_`` is needed to determine the expansion of ``*`` and ranges. The argument ``min_`` is needed to determine the expansion of ``*`` and ranges for 1-based cronspecs, such as day of month or month of year. The default is sufficient for minute, hour, and day of week. )�typer )�minr[ �value) rP rg r% r r} rx r � TypeError�CRON_INVALID_TYPE�formatr� r� �CRON_PATTERN_INVALID)r� rh ri �result�numberr* r* r+ r� � s � zcrontab._expand_cronspecr r )r? � next_hour� next_minuter( c s0 t �jd�� t�j��t�j��ddddd�dd��ddddd�����fdd� �d d �� ����fd d � }�j�jv r�t��j�� _t ��j�� _ n(d � _t��j�� _ � j t ��kr�d � _ |� t � j�� j �� j d�}|� � d �jv r��q � jd7 _|� q�t� j�� j �� j ��d d d�S )aZ Find next delta. Takes a :class:`~datetime.datetime` of last run, next minute and hour, and returns a :class:`~celery.utils.time.ffwd` for the next scheduled day and time. Only called when ``day_of_month`` and/or ``month_of_year`` cronspec is specified to further limit scheduled task execution. )�yearrg rE )r� �month�dayr( c S s, zt | ||d� W n ty& Y dS 0 dS )N�r� r� r� TF)r r� r� r* r* r+ �day_out_of_range� s z0crontab._delta_to_next.<locals>.day_out_of_rangec s �j t| ||���dd�� k S )NFrH )r r r� )r? r� r� r9 r* r+ �is_before_last_run� s ��z2crontab._delta_to_next.<locals>.is_before_last_runrJ r; c s� t d�D ]�} � jt��kpL�� j�� j �� j �pL�� j�� j �� j �}|r�d� _� jd7 _� jt��kr�d� _� jd7 _q q�qtd��d S )Ni� r r z:unable to rollover, time specification is probably invalid)r� �domr� r� �moy� RuntimeError)�_�flag)�datedatar� � days_of_monthr� �months_of_yearr* r+ � roll_over� s( ����z)crontab._delta_to_next.<locals>.roll_overr r� r� r )r� r� r� r� r� �second� microsecond)r r� �sortedr� r� r� r r� r� r r� r� r � isoweekdayr� r )r9 r? r� r� r� �thr* ) r� r� r� r� r? r� r� r� r9 r+ �_delta_to_next� s< ��zcrontab._delta_to_nextr; c C s t �| �S r7 )� CRON_REPRr� r= r* r* r+ ra s zcrontab.__repr__z0tuple[type, tuple[str, str, str, str, str], Any]c C s" | j | j| j| j| j| jf| jfS r7 )rZ r� r� r� r� r� r� r= r* r* r+ rb s ��zcrontab.__reduce__zMapping[str, Any])�stater( c s t � jf i |�� d S r7 )rX r: )r9 r� rY r* r+ � __setstate__! s zcrontab.__setstate__Nz tzinfo | Noner� z tuple[datetime, Any, datetime])r? rI r r( c s� | � ���| � | �� �}��� d � �j| jv oD�j| jv oD� | jv }|o��j|jko��j|jko��j|jko��j | j v o��j t | j �k }|r�t �fdd�| j D ��}||ddd�}n�t | j �}|o҈j t | j �k } | �rt �fdd�| j D ��} || |ddd�}n�t | j �} | j dk�o"| jdk} | �r|t � fd d �| jD ��pF| j�} | � k} || �r`d �pbd| d d | |ddd �}n| ��| |�}| ���|| �|�fS ) Nr� c 3 s | ]}|� j kr|V qd S r7 )r� )�.0r� �r? r* r+ � <genexpr>= s �z*crontab.remaining_delta.<locals>.<genexpr>r )r� r� r� c 3 s | ]}|� j kr|V qd S r7 )r� )r� r� r� r* r+ r� F s �)r� r� r� r� r) c s g | ]}|� kr|�qS r* r* )r� r� )�dow_numr* r+ � <listcomp>O s �z+crontab.remaining_delta.<locals>.<listcomp>r )�weeksr r� r� r� r� )r r< r� r� r� r� r� r� r� r� r� r[ r� r� r� r� rM )r9 r? rI r r< Zexecute_this_dateZexecute_this_hourr� �deltaZ execute_todayr� Z all_dom_moyZnext_dayZadd_weekr* )r� r? r+ �remaining_delta& sh �� � � � �� �� �� � �zcrontab.remaining_deltar )r? r r( c C s t | j||d�� S )z�Estimate of next run time. Returns when the periodic task should run next as a :class:`~datetime.timedelta`. )r )r r� )r9 r? r r* r* r+ rC ` s zcrontab.remaining_estimaterD r> c C s� | � |�}|�� }t|d�}|dk}| jjj}d}|dur�|}|} |dk rv|t|� }| � |�}|�� }|dk rB|} qB| |k}|r�d}|s�|r�| � | �� �}t|�� d�}t||�S )a� Return tuple of ``(is_due, next_time_to_run)``. If :setting:`beat_cron_starting_deadline` has been specified, the scheduler will make sure that the `last_run_at` time is within the deadline. This prevents tasks that could have been run according to the crontab, but didn't, from running again unexpectedly. Note: Next time to run is in seconds. SeeAlso: :meth:`celery.schedules.schedule.is_due` for more information. r FN) rC r\ r[ r6 rK Zbeat_cron_starting_deadline�absr< r! ) r9 r? r^ Zrem_secs�rem�dueZ deadline_secsZhas_passed_deadlineZlast_date_checkedZlast_feasible_rem_secsr* r* r+ r# k s, zcrontab.is_duerE rN c sV t |t�rR|j| jkoP|j| jkoP|j| jkoP|j| jkoP|j| jkoPt� �|�S t S r7 ) rP r r� r� r� r� r� rX rS rQ rR rY r* r+ rS � s � � � � �zcrontab.__eq__)r) r) r) r) r) )r )r- r. r/ r0 r: � staticmethodr� r� ra rb r� r r� rC r# rS re r* r* rY r+ r > s$ M � �.M�;� 1r Fz&int | float | timedelta | BaseSchedulerE r3 z float | timedelta | BaseSchedule)r' rV r6 r( c C sB | dur>t | ttf�r t| d�} t | t�r8t| ||d�S || _| S )z;Return schedule from number, timedelta, or actual schedule.N)r] )r6 )rP �floatrg r r r6 )r' rV r6 r* r* r+ r � s r c s� e Zd ZdZh d�Zdddddddddd � Zd d d d d d d d d d � Zd d d dddd d d d � Zdddddd�� fdd� Zdd�dd�Z dd�dd�Z d d d �d d �Z d d!d �d"d#�Z dd$d%�d&d'�Z � ZS )(r aS Solar event. A solar event can be used as the ``run_every`` value of a periodic task entry to schedule based on certain solar events. Notes: Available event values are: - ``dawn_astronomical`` - ``dawn_nautical`` - ``dawn_civil`` - ``sunrise`` - ``solar_noon`` - ``sunset`` - ``dusk_civil`` - ``dusk_nautical`` - ``dusk_astronomical`` Arguments: event (str): Solar event that triggers this task. See note for available values. lat (float): The latitude of the observer. lon (float): The longitude of the observer. nowfun (Callable): Function returning the current date and time as a class:`~datetime.datetime`. app (Celery): Celery app instance. > � dusk_nautical� solar_noon�sunrise� dawn_civil� dawn_nautical�sunset�dawn_astronomical�dusk_astronomical� dusk_civilz-18z-12z-6z-0:34�0Z18) r� r� r� r� r� r� r� r� r� Z next_risingZ next_transitZ next_settingTFr% rc r rJ )�event�lat�lonr� r( c s� t d�| _|| _|| _|| _t� jf i |�� || jvrVtt j |d� t | j��d���|dk sf|dkrvtt j |d���|dk s�|dkr�ttj |d ���| j�� }t|�|_t|�|_d |_| j| |_d |_|| _| j| | _| j| | _d S ) N�ephemz, )r� Z all_eventsi�����Z )r� iL���� )r� r )� __import__r� r� r� r� rX r: � _all_eventsr� �SOLAR_INVALID_EVENTr� �joinr� �SOLAR_INVALID_LATITUDE�SOLAR_INVALID_LONGITUDEZObserverr% Zelev� _horizonsZhorizonZpressure�cal�_methods�method� _use_center_l� use_center)r9 r� r� r� r� r� rY r* r+ r: s, � zsolar.__init__z1tuple[type, tuple[str, int | float, int | float]]r; c C s | j | j| j| jffS r7 )rZ r� r� r� r= r* r* r+ rb s zsolar.__reduce__c C s d� | j| j| j�S )Nz)<solar: {} at latitude {}, longitude: {}>)r� r� r� r� r= r* r* r+ ra ! s �zsolar.__repr__r r r> c C s� | � |�}t|tj�}|| j_zH| jrHt| j| j�| j � � || jd�}n t| j| j�| j � � |d�}W n2 | j j y� | j� | j � � �t dd� }Y n0 | � |�� �}| � | �� �}|| }|S )a2 Return estimate of next time to run. Returns: ~datetime.timedelta: when the periodic task should run next, or if it shouldn't run today (e.g., the sun does not rise today), returns the time when the next check should take place. )�startr� )r� r )�minutes)r r r �utcr� �dater� �getattrr� r� �SunZCircumpolarErrorZnext_antitransitr r r< )r9 r? Zlast_run_at_utcZnext_utcr$ r< r� r* r* r+ rC & s* � � ��zsolar.remaining_estimaterD c C sJ | � |�}t|�� d�}|dk}|r@| � | �� �}t|�� d�}t||�S )z�Return tuple of ``(is_due, next_time_to_run)``. Note: next time to run is in seconds. See Also: :meth:`celery.schedules.schedule.is_due` for more information. r )rC r[ r\ r< r! )r9 r? r^ r� r� r* r* r+ r# I s z solar.is_duerE rN c C s2 t |t�r.|j| jko,|j| jko,|j| jkS tS r7 )rP r r� r� r� rQ rR r* r* r+ rS Z s � �z solar.__eq__)r- r. r/ r0 r� r� r� r� r: rb ra rC r# rS re r* r* rY r+ r � sL � � � #r )FN)4r0 � __future__r rl r r � collectionsr �collections.abcr r r r �typingr r r r Zkombu.utils.objectsr Zceleryr � r Zutils.collectionsr Z utils.timer r r r r r r r �__all__r! r� r� r� r� r� r� r, � Exceptionr r1 r r r r r r* r* r* r+ �<module> s@ ( .U| n �
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка