Skip to content

Upgrading croniter 6 to 7

Breaking6.2.4 → 7.0.0Breaking2Fixed13Other17

BreakingUpgrade verdict

2 breaking changes.

  • A cron expression with a seconds field that sets the day of month to 0 is now an error rather than being silently changed to 1.
  • When expanding from a start time, the result now gives the phase within the cycle instead of the cycle's start and end bounds.
2 items need code or config changes

Installs 2 packages in all (was 3).

No longer installs six.

Moves python-dateutil 3.0.0 → 4.0.0. Your build may pick other versions.

Breaking2
Rejects day-of-month 0 in the 6-field seconds form instead of rewriting it to 1.
Makes expand_from_start_time supply the phase of a cycle, not its bounds.
expand_from_start_time

Generated by DepDelta from published Python source. Not mixed with prose notes.

  • changed: static method croniter.expand(expr_format: str, hash_id: Optional[Union[bytes, str]]=…, second_at_beginning: bool=…, from_timestamp: Optional[float]=…, strict: bool=…, strict_year: Optional[Union[int, list[int]]]=…) -> tuple[list[ExpandedExpression], dict[int, set[int]]] → static method croniter.expand(expr_format: str, hash_id: Optional[Union[bytes, str]]=…, second_at_beginning: bool=…, from_timestamp: Optional[float]=…, from_timestamp_tz: Optional[datetime.tzinfo]=…, strict: bool=…, strict_year: Optional[Union[int, list[int]]]=…) -> tuple[list[ExpandedExpression], dict[int, set[int]]]
  • added: variable field_re