You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Scheduler's CronSpec does not work with datetime.timezone offset #605
When serializing and subsequently validating CronSpec with offset as datetime.timezone, the validated instance contains string representation of the offset, which is not valid:
Activity
s3rius commentedon Apr 10, 2026
It seems like a pydantic bug, actually. I'd not expect it to be serialized to such a weird value, actually. I'm not even sure what
PT{n}Hmeans.But I agree that actually it's quite unexpected.
Here's a pydantic issue:
pydantic/pydantic#7095