Skip to content
Snippets Groups Projects
Commit 444c702a authored by Dennis Ahrens's avatar Dennis Ahrens
Browse files

Fix serialization of datetime objects

parent f54e9e2c
No related branches found
No related tags found
No related merge requests found
...@@ -35,7 +35,7 @@ WORKER_GRACEFUL_STOP_TIMEOUT = timedelta(seconds=60) ...@@ -35,7 +35,7 @@ WORKER_GRACEFUL_STOP_TIMEOUT = timedelta(seconds=60)
# stuff you probably don't want to touch: # stuff you probably don't want to touch:
BLOCKED_CONNECTION_TIMEOUT = timedelta(seconds=20) # weird stuff to avoid deadlocks, see pika documentation BLOCKED_CONNECTION_TIMEOUT = timedelta(seconds=20) # weird stuff to avoid deadlocks, see pika documentation
DATETIME_FORMAT = "%Y-%m-%dT%H:%M:%S.%f%Z%z" # serialization, both %Z%z for compatibility in case we ever want to improve timezone-related stuff DATETIME_FORMAT = "%Y-%m-%dT%H:%M:%S.%f%z" # serialization
DATE_FORMAT = "%Y-%m-%d" # serialization DATE_FORMAT = "%Y-%m-%d" # serialization
......
  • Art :lizard: @lukyanch ·

    Might you enlighten me, what exactly is fixed here? @ahrensde

  • Author

    We had serialization problems when the stuff went live. Our productive environment was unable to deserialize datetime objects properly.

    The real fix I did not understand in detail, but you said it is fine. :)

0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment