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
bug: replace strptime() with ISO parsers for date/time parsing #784
After some digging, I found that date.fromisoformat() is stricter than the previous strptime(..., "%Y-%m-%d") behavior. The previous implementation accepted dates with single-digit month/day components, such as 2024-5-2, whereas fromisoformat() rejects them and returns None.
Since this changes previously supported behavior and the goal is to maintain compatibility, I think it would be better to retain the existing functionality by normalizing the components before calling fromisoformat() (or retaining a compatibility fallback), along with a regression test for this case.
Activity
github-actions commentedon Sep 12, 2026
Hi Lakshay Chauhan (@nos1dot618), thank you for opening this issue!
Our team will review it shortly. We aim to triage all new issues within 24-48 hours and get back to you.
If you have additional information to share, please feel free to update the issue.
Thank you for your patience!
nos1dot618 commentedon Sep 12, 2026
After some digging, I found that
date.fromisoformat()is stricter than the previousstrptime(..., "%Y-%m-%d")behavior. The previous implementation accepted dates with single-digit month/day components, such as2024-5-2, whereasfromisoformat()rejects them and returnsNone.Since this changes previously supported behavior and the goal is to maintain compatibility, I think it would be better to retain the existing functionality by normalizing the components before calling
fromisoformat()(or retaining a compatibility fallback), along with a regression test for this case.