HEX

File: //home/arjun/projects/env/lib/python3.10/site-packages/celery/__pycache__/schedules.cpython-310.pyc
o

-we}�@sddZddlmZddlZddlmZmZddlmZddlm	Z	ddl
m
Z
mZmZddl
mZmZmZmZdd	lmZdd
lmZddlmZdd
lmZddlmZmZmZmZmZm Z m!Z!m"Z"dZ#edd�Z$dZ%dZ&dZ'dZ(dZ)dZ*d2dd�Z+Gdd�de,�Z-Gdd �d �Z.Gd!d"�d"e.�Z/Gd#d$�d$�Z0Gd%d&�d&e.�Z1	'	d3d4d.d/�Z2Gd0d1�d1e.�Z3dS)5z;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}.�s�str�returncCs|durdS|S)N�*�)r%r)r)�I/home/arjun/projects/env/lib/python3.10/site-packages/celery/schedules.py�	cronfield7�r+c@seZdZdZdS)rzARaised by :class:`crontab_parser` when the input can't be parsed.N)�__name__�
__module__�__qualname__�__doc__r)r)r)r*r;src@s�eZdZd)d*dd�Zd+d
d�Zd,dd�Zd-dd�Z	d.d/dd�Zed0dd��Z	e	j
d1dd��Z	ed2dd ��Zed3d!d"��Z
d4d#d$�Zd5d'd(�ZdS)6�BaseScheduleN�nowfun�Callable | None�app�
Celery | NonecCs||_||_dS�N)r2�_app)�selfr2r4r)r)r*�__init__As
zBaseSchedule.__init__r'rcCs|jp|jj�Sr6)r2r4�now�r8r)r)r*r:Er,zBaseSchedule.now�last_run_atrcC�t��r6��NotImplementedError�r8r<r)r)r*�remaining_estimateH�zBaseSchedule.remaining_estimate�tuple[bool, datetime]cCr=r6r>r@r)r)r*r#KrBzBaseSchedule.is_dueT�dt�naive_as_utc�boolcCst||j|d�S)N�rE)r�tz)r8rDrEr)r)r*rN�zBaseSchedule.maybe_make_awarercCs|jpt��Sr6)r7r�_get_current_objectr;r)r)r*r4RszBaseSchedule.app�NonecCs
||_dSr6)r7)r8r4r)r)r*r4V�
r	cCs|jjSr6)r4rr;r)r)r*rHZszBaseSchedule.tzcCs
|jjjSr6)r4�conf�
enable_utcr;r)r)r*�utc_enabled^rLzBaseSchedule.utc_enabledcCs|jst�|�S|Sr6)rOr�to_local_fallback)r8rDr)r)r*�to_localbs
zBaseSchedule.to_local�otherr
cCst|t�r|j|jkStSr6)�
isinstancer1r2�NotImplemented�r8rRr)r)r*�__eq__gs
zBaseSchedule.__eq__)NN)r2r3r4r5)r'r�r<rr'r�r<rr'rC)T)rDrrErFr'r)r'r)r4rr'rK)r'r	)r'rF)rDrr'r�rRr
r'rF)r-r.r/r9r:rAr#r�propertyr4�setterrrHrOrQrVr)r)r)r*r1?s"


�
r1cs�eZdZUdZdZded<			d'd(�fdd�
Zd)dd�Zd*dd�Zd+dd�Z	d,dd�Z
d-d d!�Zed.d#d$��Z
ed+d%d&��Z�ZS)/ra�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.
    FrF�relativeN�	run_every�float | timedelta | Noner2r3r4r5r'rKcs$t|�|_||_t�j||d�dS)N)r2r4)rr]r\�superr9)r8r]r\r2r4��	__class__r)r*r9{s
zschedule.__init__r<rrcCs"t|�|�|j|�|���|j�Sr6)rrr]r:r\r@r)r)r*rA�s�zschedule.remaining_estimaterCcCsD|�|�}|�|�}t|��d�}|dkrtd|jd�Std|d�S)aGReturn 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.
        rTr"F)rrA�max�
total_secondsr!�seconds)r8r<�	rem_delta�remaining_sr)r)r*r#�s

zschedule.is_duer&cCsd|j�d�S)Nz<freq: �>)�
human_secondsr;r)r)r*�__repr__�szschedule.__repr__rRr
cCs t|t�r|j|jkS|j|kSr6)rSrr]rUr)r)r*rV�s

zschedule.__eq__�4tuple[type, tuple[timedelta, bool, Callable | None]]cC�|j|j|j|jffSr6)rar]r\r2r;r)r)r*�
__reduce__�szschedule.__reduce__�int | floatcCst|j��d�S)Nr)rbr]rcr;r)r)r*rd�rIzschedule.secondscCs
t|j�Sr6)rrdr;r)r)r*rh�rLzschedule.human_seconds)NFNN)
r]r^r\rFr2r3r4r5r'rKrWrX�r'r&rY)r'rj)r'rm)r-r.r/r0r\�__annotations__r9rAr#rirVrlrZrdrh�
__classcell__r)r)r`r*rms 
�


%

rc@sreZdZdZeZdZdZdZd&d'd
d�Zd(dd�Z	d)dd�Z
d*dd�Zd*dd�Zd*dd�Z
d+d d!�Zd,d#d$�Zd%S)-ra�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�max_�int�min_cCsj||_||_t�|j|j�|jft�|j�|jft�|j|j�|j	ft�d|jd�|j
ff|_dS)N�^�$)rrrt�re�compile�_range�_steps�_range_steps�
_expand_range�_star�_star_steps�_expand_star�pats)r8rrrtr)r)r*r9�s
�zcrontab_parser.__init__�specr&r'�set[int]cCs:t�}|�d�D]}|s|�d��|t|�|��O}q|S)N�,z
empty part)�set�splitr�_parse_part)r8r��acc�partr)r)r*�parses
zcrontab_parser.parser��	list[int]cCs:|jD]\}}|�|�}|r||���Sq|�|f�Sr6)r��match�groupsr|)r8r��regex�handler�mr)r)r*r�
s
�zcrontab_parser._parse_part�toks�
Sequence[str]cCsr|�|d�}t|�dkr6|�|d�}||kr-tt||j|j��tt|j|d��Stt||d��S|gS)Nrr)�_expand_number�len�list�rangertrr)r8r��fr�tor)r)r*r|s�zcrontab_parser._expand_rangecCsBt|�dks
|ds|�d��|�|dd��ddt|d��S)N���empty filter)r�rr|rs�r8r�r)r)r*r{s
$zcrontab_parser._range_stepscCs0|r|ds|�d��|��ddt|d��S)Nrr�)rrrsr�r)r)r*r~ s
zcrontab_parser._star_steps�argsr
cGstt|j|j|j��Sr6)r�r�rtrr)r8r�r)r)r*r%szcrontab_parser._expand_starr%cCs�t|t�r|ddkr|�d��zt|�}Wnty5zt|�}Wnty2td|�d���wYnw|j|jd}||krMtd|�d|�d���||jkr^td	|�d
|j�d���|S)Nr�-znegative numbers not supportedzInvalid weekday literal �.rzInvalid end range: z > zInvalid beginning range: z < )	rSr&rrs�
ValueErrorr�KeyErrorrtrr)r8r%�i�max_valr)r)r*r�(s,
����
�zcrontab_parser._expand_numberN)rqr)rrrsrtrs)r�r&r'r�)r�r&r'r�)r�r�r'r�)r�r
r'r�)r%r&r'rs)r-r.r/r0rryrzr}r9r�r�r|r{r~rr�r)r)r)r*r�s/







rcs�eZdZdZ		d9d:�fd
d�
Ze	d;d<dd��Zd=dd�Zd>dd �Zd?d"d#�Z	d@�fd&d'�Z
d(efdAd-d.�ZefdBd0d1�Z
dCd3d4�ZdD�fd7d8�Z�ZS)Era�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(�minuter&�hour�day_of_week�day_of_month�
month_of_year�kwargsr
r'rKcs�t|�|_t|�|_t|�|_t|�|_t|�|_||_|�|d�|_|�|d�|_	|�|d�|_
|�|dd�|_|�|dd�|_t
�jdi|��dS)N�rq��r�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�r_r9)r8r�r�r�r�r�r�r`r)r*r9�s




zcrontab.__init__r�cronspec�int | str | Iterablerrrsrt�set[Any]cCs�t|t�r	|h}n*t|t�rt||��|�}nt|t�r|}nt|t�r)t|�}n
ttj	t
|�d���|D]}|||ksA||krOttj	||d||d���q5|S)aExpand 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)�minrb�value)
rSrsr&rr�r�r�	TypeError�CRON_INVALID_TYPE�formatr�r��CRON_PATTERN_INVALID)r�rrrt�result�numberr)r)r*r��s 




��zcrontab._expand_cronspecr<r�	next_hour�next_minuterc	st�jd��t�j��t�j��ddd	��d����fd
d��d�����fd
d�}�j�jvr?t��j��_t	��j��_
nd�_t��j��_
�j
t��krSd�_
|�	t�j��j
��jd�}|�
�d�jvron�jd7_|�qWt�j��j
��j��ddd�S)aZFind 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.
        )�yearr�rs�month�dayr'rFcSs*z
t|||d�WdStyYdSw)N�r�r�r�TF)rr�r�r)r)r*�day_out_of_range�s��z0crontab._delta_to_next.<locals>.day_out_of_rangecs�jt|||���dd��kS)NFrG)rrr�)r<r�r�r8r)r*�is_before_last_run�s��z2crontab._delta_to_next.<locals>.is_before_last_runrKcs�td�D]C}�jt��kp&��j��j��j�p&��j��j��j�}|rEd�_�jd7_�jt��krDd�_�jd7_qdStd��)Ni�rrz: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_overrrr�r�)r�r�r�r�r��second�microsecondN)r�rsr�rsr�rsr'rF)r'rK)rr��sortedr�r�r�rr�r�rr�r�r�
isoweekdayr�r)r8r<r�r�r��thr))	r�r�r�r�r<r�r�r�r8r*�_delta_to_next�s@


��	�zcrontab._delta_to_nextcCs
t�|�Sr6)�	CRON_REPRr�r;r)r)r*ris
zcrontab.__repr__�0tuple[type, tuple[str, str, str, str, str], Any]cCs"|j|j|j|j|j|jf|jfSr6)rar�r�r�r�r�r�r;r)r)r*rls��zcrontab.__reduce__�state�Mapping[str, Any]cst�jdi|��dS)Nr))r_r9)r8r�r`r)r*�__setstate__!szcrontab.__setstate__NrH�
tzinfo | Noner��tuple[datetime, Any, datetime]cs�|����|�|���}���d��j|jvo"�j|jvo"�|jv}|oD�j|jkoD�j|jkoD�j|jkoD�j	|j	voD�j
t|j
�k}|r[t�fdd�|j
D��}||ddd�}ndt|j
�}|oi�j	t|j	�k}	|	r�t�fdd�|j	D��}
||
|ddd�}n>t|j	�}
|j
dko�|jdk}|r�t�fd	d
�|jD�p�|j�}|�k}
||
r�dp�d|dd|
|ddd�}n|��|
|�}|���||�|�fS)
Nr�c3��|]
}|�jkr|VqdSr6)r�)�.0r��r<r)r*�	<genexpr>=��
��z*crontab.remaining_delta.<locals>.<genexpr>r)r�r�r�c3r�r6)r�)r�r�r�r)r*r�Fr�)r�r�r�r�r(csg|]}|�kr|�qSr)r))r�r�)�dow_numr)r*�
<listcomp>Os�z+crontab.remaining_delta.<locals>.<listcomp>r)�weeksrr�r�r�r�)rr:r�r�r�r�r�r�r�r�r�rbr�r�r�r�rQ)r8r<rHrr:�execute_this_date�execute_this_hourr��delta�
execute_todayr��all_dom_moy�next_day�add_weekr))r�r<r*�remaining_delta&sh

��
�
�
�
��	
��

��

�	�zcrontab.remaining_deltarcCst|j||d��S)z�Estimate of next run time.

        Returns when the periodic task should run next as a
        :class:`~datetime.timedelta`.
        )r)rr�)r8r<rr)r)r*rA`s	zcrontab.remaining_estimaterCc
Cs�|�|�}|��}t|d�}|dk}|jjj}d}|durG|}|}	|dkr>|t|�}|�|�}|��}|dkr:|}	|dks%|	|k}|rGd}|sK|rY|�|���}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.
        rFN)	rArcrbr4rM�beat_cron_starting_deadline�absr:r!)
r8r<re�rem_secs�rem�due�
deadline_secs�has_passed_deadline�last_date_checked�last_feasible_rem_secsr)r)r*r#ks.



�

zcrontab.is_duerRrFcsVt|t�r)|j|jko(|j|jko(|j|jko(|j|jko(|j|jko(t��|�St	Sr6)
rSrr�r�r�r�r�r_rVrTrUr`r)r*rV�s

�
�
�
�
�zcrontab.__eq__)r(r(r(r(r()r�r&r�r&r�r&r�r&r�r&r�r
r'rK)r)r�r�rrrsrtrsr'r�)r<rr�rsr�rsr'rrn)r'r�)r�r�r'rK)r<rrHr�rr�r'r�)r<rrr�r'rrXrY)r-r.r/r0r9�staticmethodr�r�rirlr�rr�rAr#rVrpr)r)r`r*r>s&M��
.
M
�;�
1rF�&int | float | timedelta | BaseScheduler\rFr4r5� float | timedelta | BaseSchedulecCsB|durt|ttf�rt|d�}t|t�rt|||d�S||_|S)z;Return schedule from number, timedelta, or actual schedule.N)rd)r4)rS�floatrsrrr4)r%r\r4r)r)r*r�s

rc
s�eZdZdZhd�Zdddddddddd	�	Zd
d
d
d
dddddd	�	Zd
d
d
dddd
d
d
d	�	Zd+�fdd�Zd,dd�Z	d-dd�Z
d.d"d#�Zd/d%d&�Zd0d)d*�Z
�ZS)1r aSSolar 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.
    >	�sunset�sunrise�
dawn_civil�
dusk_civil�
solar_noon�
dawn_nautical�
dusk_nautical�dawn_astronomical�dusk_astronomicalz-18z-12z-6z-0:34�0�18)	rrr�r�r�r�r�rr�next_rising�next_transit�next_settingTF�eventr&�latrm�lonr�r
r'rKcs�td�|_||_||_||_t�jdi|��||jvr+tt	j
|d�t|j��d���|dks3|dkr;tt
j
|d���|dksC|dkrKttj
|d	���|j��}t|�|_t|�|_d
|_|j||_d
|_||_|j||_|j||_dS)N�ephemz, )r	�
all_eventsi�����Z)r
iL����)rrr))�
__import__rr	r
rr_r9�_all_eventsr��SOLAR_INVALID_EVENTr��joinr��SOLAR_INVALID_LATITUDE�SOLAR_INVALID_LONGITUDE�Observerr&�elev�	_horizons�horizon�pressure�cal�_methods�method�
_use_center_l�
use_center)r8r	r
rr�rr`r)r*r9s,

�


zsolar.__init__�1tuple[type, tuple[str, int | float, int | float]]cCrkr6)rar	r
rr;r)r)r*rlszsolar.__reduce__cCsd�|j|j|j�S)Nz)<solar: {} at latitude {}, longitude: {}>)r�r	r
rr;r)r)r*ri!s�zsolar.__repr__r<rrcCs�|�|�}t|tj�}||j_z$|jr$t|j|j�|j	�
�||jd�}nt|j|j�|j	�
�|d�}Wn|j	jyL|j�|j	�
��t
dd�}Ynw|�|���}|�|���}||}|S)a2Return 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)rrr�utcr�dater�getattrrr�Sun�CircumpolarError�next_antitransitrrr:)r8r<�last_run_at_utc�next_utcr$r:r�r)r)r*rA&s.
	�
�����zsolar.remaining_estimaterCcCsJ|�|�}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)rArbrcr:r!)r8r<rer�r�r)r)r*r#Is
	
zsolar.is_duerRrFcCs2t|t�r|j|jko|j|jko|j|jkStSr6)rSr r	r
rrTrUr)r)r*rVZs

�
�zsolar.__eq__)
r	r&r
rmrrmr�r
r'rK)r'r rnrWrXrY)r-r.r/r0rrrrr9rlrirAr#rVrpr)r)r`r*r �sN���



#r )r%r&r'r&)FN)r%r�r\rFr4r5r'r�)4r0�
__future__rrwrr�collectionsr�collections.abcrrrr	�typingr
rrr
�kombu.utils.objectsr�celeryr�r�utils.collectionsr�
utils.timerrrrrrrr�__all__r!r�r�r�rrrr+�	Exceptionrr1rrrrr r)r)r)r*�<module>sB(

.U|n�