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
We ran into the issue by using Z for UTC timezone in the datetime strings (2011-11-04T00:05:23Z) with python 3.10. Where as before 3.4 it still worked with the same input.
Hey @Yelinz,
thanks for the report. This one slipped through our tests and other checks. Sorry bout that. Will work on a fix& release for it this week.
Graphene 3.4.1 fixes an important bug regarding dealing with
datetimes in UTC, with the `Z` suffix/tz marker.
Note that the next Caluma version (not yet released as of now) will
also have this dependency pinned, but I'd like to have this fix
to ensure no stray frontend bit will trigger the bug
(graphql-python/graphene#1580)
Datetime parsing breaks for certain formats on some python versions.
Python 3.10
fromisoformat
accepted strings https://docs.python.org/3.10/library/datetime.html#datetime.datetime.fromisoformatPython 3.11
fromisoformat
accepted strings https://docs.python.org/3.11/library/datetime.html#datetime.datetime.fromisoformatWe ran into the issue by using
Z
for UTC timezone in the datetime strings (2011-11-04T00:05:23Z
) with python 3.10. Where as before 3.4 it still worked with the same input.Bug introduced by 17d09c8
The text was updated successfully, but these errors were encountered: