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
As you can see, today is the 328th day of the year, and next Saturday is the 335th day of the year. But if I tell it to parse "December 1st" then suddenly next Saturday has the same tm_yday as today.
I think this bug is with parsedatetime and not upstream because time gets it right:
I think it happens because when there's a relative date, a timedelta is added to now, so the timedelta fills in tm_yday for us. When there's an exact date, tm_yday just isn't filled in at all so it's defaulting to today's tm_yday.
First thanks for making parsedatetime. It's really great.
These are correct:
This is wrong:
As you can see, today is the 328th day of the year, and next Saturday is the 335th day of the year. But if I tell it to parse "December 1st" then suddenly next Saturday has the same tm_yday as today.
I think this bug is with parsedatetime and not upstream because
time
gets it right:The text was updated successfully, but these errors were encountered: