1436

I have a basic dict as follows:

sample = {}
sample['title'] = "String"
sample['somedate'] = somedatetimehere

When I try to do jsonify(sample) I get:

TypeError: datetime.datetime(2012, 8, 8, 21, 46, 24, 862000) is not JSON serializable

What can I do such that my dictionary sample can overcome the error above?

Note: Though it may not be relevant, the dictionaries are generated from the retrieval of records out of mongodb where when I print out str(sample['somedate']), the output is 2012-08-08 21:46:24.862000.

10
  • 1
    Is this specifically python in general, or possibly django?
    – jdi
    Commented Aug 9, 2012 at 2:05
  • 3
    It technically is specifically python, I am not using django, but retrieving records out of mongodb.
    – Rolando
    Commented Aug 9, 2012 at 2:05
  • possible duplicate of JSON datetime between Python and JavaScript
    – jdi
    Commented Aug 9, 2012 at 2:05
  • I am using mongoengine, but if pymongo has better ways of getting around this or overcoming this, please tell.
    – Rolando
    Commented Aug 9, 2012 at 2:07
  • 6
    The linked question is essentially telling you not to try to serialize the datetime object, but rather to convert it to a string in the common ISO format before serializing. Commented Aug 9, 2012 at 2:13

34 Answers 34

1768

My quick & dirty JSON dump that eats dates and everything:

json.dumps(my_dictionary, indent=4, sort_keys=True, default=str)

default is a function applied to objects that aren't serializable.
In this case it's str, so it just converts everything it doesn't know to strings. Which is great for serialization but not so great when deserializing (hence the "quick & dirty") as anything might have been string-ified without warning, e.g. a function or numpy array.

17
  • 40
    This is awesome, But unfortunately I did not understand what happened? Can anyone explain this answer? Commented Oct 4, 2016 at 5:31
  • 154
    @KishorPawar: default is a function applied to objects that aren't serializable. In this case it's str, so it just converts everything it doesn't know to strings. Which is great for serialization but not so great when deserializing (hence the "quick & dirty") as anything might have been string-ified without warning, e.g. a function or numpy array.
    – Mark
    Commented Oct 19, 2016 at 20:54
  • 3
    @Mark awesome. Thanks. Useful when you know type of those non-serializable values like dates. Commented Oct 20, 2016 at 0:32
  • 2
    Can someone share how to return back to original dictionary? Commented Dec 5, 2018 at 7:34
  • 3
    @jjmontes, doesn't work for everything, eg json.dumps({():1,type(None):2},default=str) raises TypeError, can't have type or tuple. Commented Aug 22, 2019 at 18:46
646

Building on other answers, a simple solution based on a specific serializer that just converts datetime.datetime and datetime.date objects to strings.

from datetime import date, datetime

def json_serial(obj):
    """JSON serializer for objects not serializable by default json code"""

    if isinstance(obj, (datetime, date)):
        return obj.isoformat()
    raise TypeError ("Type %s not serializable" % type(obj))

As seen, the code just checks to find out if object is of class datetime.datetime or datetime.date, and then uses .isoformat() to produce a serialized version of it, according to ISO 8601 format, YYYY-MM-DDTHH:MM:SS (which is easily decoded by JavaScript). If more complex serialized representations are sought, other code could be used instead of str() (see other answers to this question for examples). The code ends by raising an exception, to deal with the case it is called with a non-serializable type.

This json_serial function can be used as follows:

from datetime import datetime
from json import dumps

print dumps(datetime.now(), default=json_serial)

The details about how the default parameter to json.dumps works can be found in Section Basic Usage of the json module documentation.

11
  • 8
    yeah the correct answer, more pretty import datetime and if isinstance(obj, datetime.datetime) , I lost many time because don't used from datetime import datetime , anyway thanks
    – Sérgio
    Commented Sep 22, 2014 at 20:43
  • 21
    but this does not explain how to deserialise it with the correct type, isnt it ?
    – BlueTrin
    Commented Jun 26, 2015 at 15:53
  • 4
    No, @BlueTrin , nothing said about that. In my case, I'm deserializing in JavaScript, which works out of the box.
    – jgbarah
    Commented Jun 28, 2015 at 8:09
  • 2
    This will cause unexpected behavior if the json module ever updates to include serialization of datetime objects.
    – Justin
    Commented Aug 16, 2016 at 17:27
  • 2
    @serg But converting times to UTC would unify 01:00:00+01:00 and 02:00:00+00:00 which are not supposed to be the same, depending on context. They refer to the same point in time of course, but the offset might be a relevant aspect of the value.
    – Alfe
    Commented Sep 18, 2019 at 12:26
558

Updated for 2018

The original answer accommodated the way MongoDB "date" fields were represented as:

{"$date": 1506816000000}

If you want a generic Python solution for serializing datetime to json, check out @jjmontes' answer for a quick solution which requires no dependencies.


As you are using mongoengine (per comments) and pymongo is a dependency, pymongo has built-in utilities to help with json serialization:
http://api.mongodb.org/python/1.10.1/api/bson/json_util.html

Example usage (serialization):

from bson import json_util
import json

json.dumps(anObject, default=json_util.default)

Example usage (deserialization):

json.loads(aJsonString, object_hook=json_util.object_hook)

Django

Django provides a native DjangoJSONEncoder serializer that deals with this kind of properly.

See https://docs.djangoproject.com/en/dev/topics/serialization/#djangojsonencoder

from django.core.serializers.json import DjangoJSONEncoder

return json.dumps(
  item,
  sort_keys=True,
  indent=1,
  cls=DjangoJSONEncoder
)

One difference I've noticed between DjangoJSONEncoder and using a custom default like this:

import datetime
import json

def default(o):
    if isinstance(o, (datetime.date, datetime.datetime)):
        return o.isoformat()

return json.dumps(
  item,
  sort_keys=True,
  indent=1,
  default=default
)

Is that Django strips a bit of the data:

 "last_login": "2018-08-03T10:51:42.990", # DjangoJSONEncoder 
 "last_login": "2018-08-03T10:51:42.990239", # default

So, you may need to be careful about that in some cases.

20
  • 5
    Is it good/bad practice to be mixing multiple libraries i.e. having mongoengine for inserting docs and pymongo for query/retrieval?
    – Rolando
    Commented Aug 9, 2012 at 2:25
  • Its not bad practice, it just implies some dependency on the libraries that your main library uses. If you can't accomplish what you need from mongoengine, then you drop down to pymongo. Its the same with Django MongoDB. With the later, you would try to stay within the django ORM to maintain backend agnostic state. But sometimes you can't do what you need in the abstraction, so you drop down a layer. In this case, its completely unrelated to your problem since you are just using utility methods to accompany the JSON format.
    – jdi
    Commented Aug 9, 2012 at 2:29
  • I am trying this out with Flask and it appears that by using json.dump, I am unable to put a jsonify() wrapper around it such that it returns in application/json. Attempting to do return jsonify(json.dumps(sample, default=json_util.default))
    – Rolando
    Commented Aug 9, 2012 at 2:39
  • 5
    @amit Its not so much about memorizing syntax, as it is about getting good at reading documentation and storing enough info in my head to recognise where and when I need to retrieve it again. In this case, one might say "Oh a custom object with json" and then quickly refresh on that usage
    – jdi
    Commented Jul 2, 2015 at 19:12
  • 2
    @guyskk I haven't tracked changes in bjson or mongo since I wrote this 5 years ago. But if you want control over the serialisation of the datetime then you need to write your own default handler function as illustrated in the answer given by jgbarah
    – jdi
    Commented Nov 7, 2017 at 10:24
302

I have just encountered this problem and my solution is to subclass json.JSONEncoder:

from datetime import datetime
import json

class DateTimeEncoder(json.JSONEncoder):
    def default(self, o):
        if isinstance(o, datetime):
            return o.isoformat()

        return json.JSONEncoder.default(self, o)

In your call do something like: json.dumps(yourobj, cls=DateTimeEncoder) The .isoformat() I got from one of the answers above.

12
  • 31
    upped because implementing a custom JSONEncoder should be the proper way to go
    – 3k-
    Commented Aug 29, 2015 at 22:13
  • 32
    Not only should this be the top answer, this should be part of the regular json encoder. If only decoding was less ambiguous..
    – Joost
    Commented Oct 7, 2015 at 15:00
  • 6
    For those using Django, see DjangoJSONEncoder. docs.djangoproject.com/en/dev/topics/serialization/…
    – S. Kirby
    Commented Nov 17, 2016 at 7:06
  • 4
    Super helpful. Last line could be return super(DateTimeEncoder, self).default(o)
    – Bob Stein
    Commented Jan 28, 2017 at 1:48
  • 26
    With Python 3 the last line is even simpler: return super().default(o)
    – ariddell
    Commented Jan 15, 2018 at 13:20
146

Convert the date to a string

sample['somedate'] = str( datetime.utcnow() )
5
  • 11
    And how could I deserialize it in Python?
    – wobmene
    Commented Mar 27, 2014 at 12:58
  • 73
    The problem is if you have many datetime objects embedded deeply in a data structure, or they are random. This isn't a reliable method.
    – Rebs
    Commented May 10, 2014 at 6:37
  • 3
    to deserialize: oDate = datetime.datetime.strptime(sDate, '%Y-%m-%d %H:%M:%S.%f'). Formats obtained from: docs.python.org/2/library/datetime.html
    – Roman
    Commented May 11, 2015 at 10:45
  • 15
    Downvoted as it ignores timezone information. Keep in mind that .now() uses local time, without indicating this. At least .utcnow() should be used (and then a +0000 or Z appended)
    – Daniel F
    Commented Aug 25, 2015 at 20:06
  • 5
    @DanielF At least .utcnow() should be used Not exactly, datetime.now(timezone.utc) is recommended, see warning in: docs.python.org/3.8/library/….
    – Toreno96
    Commented May 19, 2020 at 10:04
86

For others who do not need or want to use the pymongo library for this, you can achieve datetime JSON conversion easily with this small snippet:

def default(obj):
    """Default JSON serializer."""
    import calendar, datetime

    if isinstance(obj, datetime.datetime):
        if obj.utcoffset() is not None:
            obj = obj - obj.utcoffset()
        millis = int(
            calendar.timegm(obj.timetuple()) * 1000 +
            obj.microsecond / 1000
        )
        return millis
    raise TypeError('Not sure how to serialize %s' % (obj,))

Then use it like so:

import datetime, json
print json.dumps(datetime.datetime.now(), default=default)

Output:

'1365091796124'
5
  • 1
    Shouldn't millis= be indented inside the if statement? It's also probably better to use str(obj) to get the ISO format which I would think is more common.
    – Rebs
    Commented May 10, 2014 at 6:45
  • Why would you want it to be indented? This snippet works and the resulting output can easily be deserialized/parsed from javascript.
    – Jay Taylor
    Commented May 12, 2014 at 0:29
  • 5
    Because obj may not be a [time, date, datetime] object
    – Rebs
    Commented May 13, 2014 at 2:30
  • 2
    your example is incorrect if the local timezone has non-zero UTC offset (most of them). datetime.now() returns local time (as a naive datetime object) but your code assumes that obj is in UTC if it is not timezone-aware. Use datetime.utcnow() instead.
    – jfs
    Commented Oct 12, 2014 at 23:25
  • 2
    Adjusted it to raise a type error if obj is unrecognized as per the Python documentation recommendation at docs.python.org/2/library/json.html#basic-usage.
    – Jay Taylor
    Commented Nov 5, 2015 at 18:27
71

Here is my solution:

import json

class DatetimeEncoder(json.JSONEncoder):
    def default(self, obj):
        try:
            return super().default(obj)
        except TypeError:
            return str(obj)

Then you can use it like that:

json.dumps(dictionary, cls=DatetimeEncoder)
4
  • 1
    agree. Much better, at least out of the mongodb context. You can do isinstance(obj, datetime.datetime) within the TypeError, add more types to handle, and finish up with the str(obj) or repr(obj). And all your dumps can just point to this specialized class.
    – JL Peyret
    Commented Jul 11, 2017 at 21:54
  • @Natim this solution is the best. +1
    – Souvik Ray
    Commented Nov 22, 2019 at 19:34
  • What about decoding? Commented Jul 17, 2020 at 0:53
  • @ThomasSauvajon stackoverflow.com/a/40489783/186202
    – Natim
    Commented Jul 17, 2020 at 8:16
68

If you are using Python 3.7, then the best solution is using datetime.isoformat() and datetime.fromisoformat(); they work with both naive and aware datetime objects:

#!/usr/bin/env python3.7

from datetime import datetime
from datetime import timezone
from datetime import timedelta
import json

def default(obj):
    if isinstance(obj, datetime):
        return { '_isoformat': obj.isoformat() }
    raise TypeError('...')

def object_hook(obj):
    _isoformat = obj.get('_isoformat')
    if _isoformat is not None:
        return datetime.fromisoformat(_isoformat)
    return obj

if __name__ == '__main__':
    #d = { 'now': datetime(2000, 1, 1) }
    d = { 'now': datetime(2000, 1, 1, tzinfo=timezone(timedelta(hours=-8))) }
    s = json.dumps(d, default=default)
    print(s)
    print(d == json.loads(s, object_hook=object_hook))

output:

{"now": {"_isoformat": "2000-01-01T00:00:00-08:00"}}
True

If you are using Python 3.6 or below, and you only care about the time value (not the timezone), then you can use datetime.timestamp() and datetime.fromtimestamp() instead;

If you are using Python 3.6 or below, and you do care about the timezone, then you can get it via datetime.tzinfo, but you have to serialize this field by yourself; the easiest way to do this is to add another field _tzinfo in the serialized object;

Finally, beware of precisions in all these examples;

4
  • datetime.isoformat() is also present in Python 2.7: docs.python.org/2/library/…
    – powlo
    Commented Jun 10, 2019 at 8:56
  • 1
    Very helpful solution. Could it also support datetime.time?
    – idbrii
    Commented Jul 17, 2021 at 23:16
  • 1
    @idbrii As @egvo said, you forgot default=default in your edit, which introduced the error. But you are right super().default(obj) is useless here. In fact, it came from a json-encoder example where it is useful.
    – Cyker
    Commented Jul 28, 2021 at 18:33
  • 1
    this is my favorite answer, since it a) includes deserialization and b) is very simple/easy to understand Commented Mar 13, 2023 at 16:00
38

You should apply the .strftime() method on a datetime.datetime object to make it a string.

Here's an example:

from datetime import datetime

time_dict = {'time': datetime.now().strftime('%Y-%m-%dT%H:%M:%S')}
sample_dict = {'a': 1, 'b': 2}
sample_dict.update(time_dict)
sample_dict

Output:

Out[0]: {'a': 1, 'b': 2, 'time': '2017-10-31T15:16:30'}

[UPDATE]:

In Python 3.6 or later, you can simply use the .isoformat() method:

from datetime import datetime

datetime.now().isoformat()
4
  • how to encode this ? Commented Mar 23, 2023 at 8:31
  • "Update" or similar does not belong in posts (near "Changelogs"). There is a full revision history on this platform. The answer should be as if it was written right now. Commented Oct 30, 2023 at 14:59
  • @PeterMortensen why do you add some wrong information to the answer?! isoformat() exists in python3.6 not just version 3.7 onwards. I think you've confused it with fromisoformat() instead. BTW, I know about the history of posts, but I usually do that to indicate that this part of the answer is newer to a reader for better attention. Commented Oct 30, 2023 at 15:17
  • @BikashCocboy what do you mean by encode? you mean convert it back from string to datetime? if so you can simply use datetime.datetime.fromisoformat('2017-10-31T15:16:30') Commented Nov 13, 2023 at 17:21
34

The json.dumps method can accept an optional parameter called default which is expected to be a function. Every time JSON tries to convert a value it does not know how to convert, it will call the function we passed to it. The function will receive the object in question, and it is expected to return the JSON representation of the object.

def myconverter(o):
  if isinstance(o, datetime.datetime):
    return o.__str__()

print(json.dumps(d, default = myconverter))
2
  • Love this, it's very compact. However, I'm using o.isoformat().
    – Nick K9
    Commented Apr 16, 2023 at 17:23
  • This feature should be more widely used!
    – Kevin R.
    Commented Mar 19 at 2:39
22

I have an application with a similar issue; my approach was to JSONize the datetime value as a 6-item list (year, month, day, hour, minutes, seconds); you could go to microseconds as a 7-item list, but I had no need to:

class DateTimeEncoder(json.JSONEncoder):
    def default(self, obj):
        if isinstance(obj, datetime.datetime):
            encoded_object = list(obj.timetuple())[0:6]
        else:
            encoded_object =json.JSONEncoder.default(self, obj)
        return encoded_object

sample = {}
sample['title'] = "String"
sample['somedate'] = datetime.datetime.now()

print sample
print json.dumps(sample, cls=DateTimeEncoder)

produces:

{'somedate': datetime.datetime(2013, 8, 1, 16, 22, 45, 890000), 'title': 'String'}
{"somedate": [2013, 8, 1, 16, 22, 45], "title": "String"}
2
  • Fails to work if the time saved is saved by doing datetime.utcnow()
    – saurshaz
    Commented Sep 5, 2013 at 6:34
  • 1
    What error are you seeing with datetime.utcnow()? It works okay for me.
    – codingatty
    Commented Dec 10, 2013 at 1:54
21

My solution (with less verbosity, I think):

def default(o):
    if type(o) is datetime.date or type(o) is datetime.datetime:
        return o.isoformat()

def jsondumps(o):
    return json.dumps(o, default=default)

Then use jsondumps instead of json.dumps. It will print:

>>> jsondumps({'today': datetime.date.today()})
'{"today": "2013-07-30"}'

I you want, later you can add other special cases to this with a simple twist of the default method. Example:

def default(o):
    if type(o) is datetime.date or type(o) is datetime.datetime:
        return o.isoformat()
    if type(o) is decimal.Decimal:
        return float(o)
7
  • 1
    You should use isinstance(o, (datetime.date, datetime.datetime,)). Probably wouldn't hurt to include datetime.time too.
    – Rebs
    Commented May 10, 2014 at 6:56
  • I don't think this is a good solution anymore. Probably the conversions should take a more privileged place -- and also a more understandable place -- in your code, so you know what you are converting to when you put things into a database, or whatever, instead of having everything being done by a transparent function. But I don't know.
    – fiatjaf
    Commented May 10, 2014 at 11:31
  • 2
    JSON is good for serialising data for processing later. You may not know exactly what that data is. And you shouldn't need to. Serialising JSON should just work. Just like converting unicode to ascii should. Python's inability to do this without obscure functions makes it annoying to use. Database validation is a separate issue IMO.
    – Rebs
    Commented May 11, 2014 at 11:52
  • No, it shouldn't "just work". If you don't know how the serialization occurred and has to access the data later from another program/language, then you're lost.
    – fiatjaf
    Commented May 12, 2014 at 1:45
  • 2
    JSON is commonly used for strings, ints, floats, dates (I'm sure others use currency, temperatures, commonly too). But datetime is part of the standard library and should support de/serialisation. If it wasn't for this question, I'd still be manually searching my incredibly complex json blobs (which I didn't always create the structure for) for dates and serialising them 1 by 1.
    – Rebs
    Commented May 13, 2014 at 3:11
21

This question repeats time and time again—a simple way to patch the json module such that serialization would support datetime.

import json
import datetime

json.JSONEncoder.default = lambda self,obj: (obj.isoformat() if isinstance(obj, datetime.datetime) else None)

Then use JSON serialization as you always do, this time with datetime being serialized as isoformat.

json.dumps({'created':datetime.datetime.now()})

Resulting in: '{"created": "2015-08-26T14:21:31.853855"}'

See more details and some words of caution at: Stack Overflow: JSON datetime between Python and JavaScript

2
  • Monkey patch FTW. The nasty thing is of course that this modifies the behaviour of the json module in your whole application, which may surprise others in a large application, so should generally be used with care imho. Commented Feb 10, 2019 at 19:16
  • Note that this solution will only work for datetime objects. Dates will be encoded as null. To fix this, the code can be changed to: json.JSONEncoder.default = lambda self, obj: (obj.isoformat() if isinstance(obj, datetime.date) else None) Commented Apr 6 at 13:13
11

Here is a simple solution to over come "datetime not JSON serializable" problem.

enco = lambda obj: (
    obj.isoformat()
    if isinstance(obj, datetime.datetime)
    or isinstance(obj, datetime.date)
    else None
)

json.dumps({'date': datetime.datetime.now()}, default=enco)

Output:-> {"date": "2015-12-16T04:48:20.024609"}

11

You have to supply a custom encoder class with the cls parameter of json.dumps. To quote from the documentation:

>>> import json
>>> class ComplexEncoder(json.JSONEncoder):
...     def default(self, obj):
...         if isinstance(obj, complex):
...             return [obj.real, obj.imag]
...         return json.JSONEncoder.default(self, obj)
...
>>> dumps(2 + 1j, cls=ComplexEncoder)
'[2.0, 1.0]'
>>> ComplexEncoder().encode(2 + 1j)
'[2.0, 1.0]'
>>> list(ComplexEncoder().iterencode(2 + 1j))
['[', '2.0', ', ', '1.0', ']']

This uses complex numbers as the example, but you can just as easily create a class to encode dates (except I think JSON is a little fuzzy about dates).

7

Actually it is quite simple. If you need to often serialize dates, then work with them as strings. You can easily convert them back as datetime objects if needed.

If you need to work mostly as datetime objects, then convert them as strings before serializing.

import json, datetime

date = str(datetime.datetime.now())
print(json.dumps(date))
"2018-12-01 15:44:34.409085"
print(type(date))
<class 'str'>

datetime_obj = datetime.datetime.strptime(date, '%Y-%m-%d %H:%M:%S.%f')
print(datetime_obj)
2018-12-01 15:44:34.409085
print(type(datetime_obj))
<class 'datetime.datetime'>

As you can see, the output is the same in both cases. Only the type is different.

7

I usually use orjson. Not only because of its tremendous performance, but also for its great (RFC-3339 compliant) support of datetime:

import orjson # via pip3 install orjson
from datetime import datetime

data = {"created_at": datetime(2022, 3, 1)}

orjson.dumps(data) # returns b'{"created_at":"2022-03-01T00:00:00"}'

If you would like to use datetime.datetime objects without a tzinfo as UTC you can add the related option:

orjson.dumps(data, option=orjson.OPT_NAIVE_UTC) # returns b'{"created_at":"2022-03-01T00:00:00+00:00"}'
1
  • 2
    This is a great answer. No idea why the native json module can't handle datetime when virtually all other libraries in other languages do. This should be the standard. Commented Aug 28, 2023 at 20:34
7

The simplest way to do this is to change the part of the dict that is in datetime format to isoformat. That value will effectively be a string in isoformat which json is OK with.

v_dict = version.dict()
v_dict['created_at'] = v_dict['created_at'].isoformat()
6

Try this one with an example to parse it:

#!/usr/bin/env python

import datetime
import json

import dateutil.parser  # pip install python-dateutil


class JSONEncoder(json.JSONEncoder):

    def default(self, obj):
        if isinstance(obj, datetime.datetime):
            return obj.isoformat()
        return super(JSONEncoder, self).default(obj)


def test():
    dts = [
        datetime.datetime.now(),
        datetime.datetime.now(datetime.timezone(-datetime.timedelta(hours=4))),
        datetime.datetime.utcnow(),
        datetime.datetime.now(datetime.timezone.utc),
    ]
    for dt in dts:
        dt_isoformat = json.loads(json.dumps(dt, cls=JSONEncoder))
        dt_parsed = dateutil.parser.parse(dt_isoformat)
        assert dt == dt_parsed
        print(f'{dt}, {dt_isoformat}, {dt_parsed}')
        # 2018-07-22 02:22:42.910637, 2018-07-22T02:22:42.910637, 2018-07-22 02:22:42.910637
        # 2018-07-22 02:22:42.910643-04:00, 2018-07-22T02:22:42.910643-04:00, 2018-07-22 02:22:42.910643-04:00
        # 2018-07-22 06:22:42.910645, 2018-07-22T06:22:42.910645, 2018-07-22 06:22:42.910645
        # 2018-07-22 06:22:42.910646+00:00, 2018-07-22T06:22:42.910646+00:00, 2018-07-22 06:22:42.910646+00:00


if __name__ == '__main__':
    test()
0
4

If you are working with Django models you can directly pass encoder=DjangoJSONEncoder to the field constructor. It will work like a charm.

from django.core.serializers.json import DjangoJSONEncoder
from django.db import models
from django.utils.timezone import now


class Activity(models.Model):
    diff = models.JSONField(null=True, blank=True, encoder=DjangoJSONEncoder)


diff = {
    "a": 1,
    "b": "BB",
    "c": now()
}

Activity.objects.create(diff=diff)
4

I often use IntelliJ Evaluate Expression tool during debugging to copy over certain objects to analyze them. The problem with that approach is that if dictionary that you try to dump has a date it's brakes and the other problem that you can't define a converter using that tool, so I come up with this one liner:

json.dumps(dict_to_dump, default=lambda o: o.__str__() if isinstance(o, datetime) else None)

enter image description here

1
  • dont forget to import datetime python package from datetime import datetime
    – Dhwanit
    Commented Jul 18 at 6:44
3

Generally there are several ways to serialize datetimes, like:

  1. ISO 8601 string, short and can include timezone info, e.g., jgbarah's answer
  2. Timestamp (timezone data is lost), e.g. JayTaylor's answer
  3. Dictionary of properties (including timezone).

If you're okay with the last way, the json_tricks package handles dates, times and datetimes including timezones.

from datetime import datetime
from json_tricks import dumps
foo = {'title': 'String', 'datetime': datetime(2012, 8, 8, 21, 46, 24, 862000)}
dumps(foo)

which gives:

{"title": "String", "datetime": {"__datetime__": null, "year": 2012, "month": 8, "day": 8, "hour": 21, "minute": 46, "second": 24, "microsecond": 862000}}

So all you need to do is

`pip install json_tricks`

and then import from json_tricks instead of json.

The advantage of not storing it as a single string, int or float comes when decoding: if you encounter just a string or especially int or float, you need to know something about the data to know if it's a datetime. As a dict, you can store metadata so it can be decoded automatically, which is what json_tricks does for you. It's also easily editable for humans.

Disclaimer: it's made by me. Because I had the same problem.

3

As per the jjmontes' answer, I have used the following approach. For Flask and flask-restful users

# Get JSON string
jsonStr = json.dumps(my_dictionary, indent=1, sort_keys=True, default=str)
# Then convert the JSON string to a JSON object
return json.loads(jsonStr)
1
  • 6
    This not distinct from jjmontes Answer - this should be a comment on their Answer instead.
    – cellepo
    Commented Aug 10, 2021 at 0:38
2

If you are using the result in a view be sure to return a proper response. According to the API, jsonify does the following:

Creates a Response with the JSON representation of the given arguments with an application/json mimetype.

To mimic this behavior with json.dumps you have to add a few extra lines of code.

response = make_response(dumps(sample, cls=CustomEncoder))
response.headers['Content-Type'] = 'application/json'
response.headers['mimetype'] = 'application/json'
return response

You should also return a dict to fully replicate jsonify's response. So, the entire file will look like this

from flask import make_response
from json import JSONEncoder, dumps


class CustomEncoder(JSONEncoder):
    def default(self, obj):
        if set(['quantize', 'year']).intersection(dir(obj)):
            return str(obj)
        elif hasattr(obj, 'next'):
            return list(obj)
        return JSONEncoder.default(self, obj)

@app.route('/get_reps/', methods=['GET'])
def get_reps():
    sample = ['some text', <datetime object>, 123]
    response = make_response(dumps({'result': sample}, cls=CustomEncoder))
    response.headers['Content-Type'] = 'application/json'
    response.headers['mimetype'] = 'application/json'
    return response
4
  • 1
    Question has nothing to do with flask. Commented Sep 9, 2014 at 21:16
  • 3
    The question is about python. My answer solves the question using python. The OP did not say if the solution should include or exclude certain libraries. It is also useful for anyone else reading this question who wants an alternative to pymongo.
    – reubano
    Commented Sep 10, 2014 at 7:24
  • They question is both about Python and not about Flask. Flask is not even needed in your answer to the question, so I suggest you remove it. Commented Sep 10, 2014 at 10:37
  • 1
    In flask it's much easier to use flask.json.dumps it handles datetime objects.
    – Jonatan
    Commented Jul 31, 2020 at 10:10
2

My solution ...

from datetime import datetime
import json

from pytz import timezone
import pytz


def json_dt_serializer(obj):
    """JSON serializer, by macm.
    """
    rsp = dict()
    if isinstance(obj, datetime):
        rsp['day'] = obj.day
        rsp['hour'] = obj.hour
        rsp['microsecond'] = obj.microsecond
        rsp['minute'] = obj.minute
        rsp['month'] = obj.month
        rsp['second'] = obj.second
        rsp['year'] = obj.year
        rsp['tzinfo'] = str(obj.tzinfo)
        return rsp
    raise TypeError("Type not serializable")


def json_dt_deserialize(obj):
    """JSON deserialize from json_dt_serializer, by macm.
    """
    if isinstance(obj, str):
        obj = json.loads(obj)
    tzone = timezone(obj['tzinfo'])
    tmp_dt = datetime(obj['year'],
                      obj['month'],
                      obj['day'],
                      hour=obj['hour'],
                      minute=obj['minute'],
                      second=obj['second'],
                      microsecond=obj['microsecond'])
    loc_dt = tzone.localize(tmp_dt)
    deserialize = loc_dt.astimezone(tzone)
    return deserialize    

Ok, now some tests.

# Tests
now = datetime.now(pytz.utc)

# Using this solution
rsp = json_dt_serializer(now)
tmp = json_dt_deserialize(rsp)
assert tmp == now
assert isinstance(tmp, datetime) == True
assert isinstance(now, datetime) == True

# using default from json.dumps
tmp = json.dumps(datetime.now(pytz.utc), default=json_dt_serializer)
rsp = json_dt_deserialize(tmp)
assert isinstance(rsp, datetime) == True

# Lets try another timezone
eastern = timezone('US/Eastern')
now = datetime.now(eastern)
rsp = json_dt_serializer(now)
tmp = json_dt_deserialize(rsp)

print(tmp)
# 2015-10-22 09:18:33.169302-04:00

print(now)
# 2015-10-22 09:18:33.169302-04:00

# Wow, Works!
assert tmp == now
2

Convert the date to string

date = str(datetime.datetime(somedatetimehere)) 
1
  • 1
    jjmontes answer does exactly that, but without the necessity to do it explicitly for every date... Commented Aug 17, 2017 at 11:34
2

Here is my full solution for converting datetime to JSON and back...

import calendar, datetime, json

def outputJSON(obj):
    """Default JSON serializer."""

    if isinstance(obj, datetime.datetime):
        if obj.utcoffset() is not None:
            obj = obj - obj.utcoffset()

        return obj.strftime('%Y-%m-%d %H:%M:%S.%f')
    return str(obj)

def inputJSON(obj):
    newDic = {}

    for key in obj:
        try:
            if float(key) == int(float(key)):
                newKey = int(key)
            else:
                newKey = float(key)

            newDic[newKey] = obj[key]
            continue
        except ValueError:
            pass

        try:
            newDic[str(key)] = datetime.datetime.strptime(obj[key], '%Y-%m-%d %H:%M:%S.%f')
            continue
        except TypeError:
            pass

        newDic[str(key)] = obj[key]

    return newDic

x = {'Date': datetime.datetime.utcnow(), 34: 89.9, 12.3: 90, 45: 67, 'Extra': 6}

print x

with open('my_dict.json', 'w') as fp:
    json.dump(x, fp, default=outputJSON)

with open('my_dict.json') as f:
    my_dict = json.load(f, object_hook=inputJSON)

print my_dict

Output

{'Date': datetime.datetime(2013, 11, 8, 2, 30, 56, 479727), 34: 89.9, 45: 67, 12.3: 90, 'Extra': 6}
{'Date': datetime.datetime(2013, 11, 8, 2, 30, 56, 479727), 34: 89.9, 45: 67, 12.3: 90, 'Extra': 6}

JSON File

{"Date": "2013-11-08 02:30:56.479727", "34": 89.9, "45": 67, "12.3": 90, "Extra": 6}

This has enabled me to import and export strings, ints, floats and datetime objects. It shouldn't be to hard to extend for other types.

1
  • 1
    It explodes in Python 3 with TypeError: 'str' does not support the buffer interface. It is because of 'wb' open mode, should be 'w'. It also blows in deserialization when we have data similar to date like '0000891618-05-000338' but not matching pattern.
    – omikron
    Commented Feb 14, 2014 at 16:14
1

I got the same error message while writing the serialize decorator inside a Class with sqlalchemy. So instead of :

Class Puppy(Base):
    ...
    @property
    def serialize(self):
        return { 'id':self.id,
                 'date_birth':self.date_birth,
                  ...
                }

I simply borrowed jgbarah's idea of using isoformat() and appended the original value with isoformat(), so that it now looks like:

                  ...
                 'date_birth':self.date_birth.isoformat(),
                  ...
1

A quick fix if you want your own formatting

for key,val in sample.items():
    if isinstance(val, datetime):
        sample[key] = '{:%Y-%m-%d %H:%M:%S}'.format(val) #you can add different formating here
json.dumps(sample)
0

I had encountered the same problem when externalizing a Django model object to dump as JSON.

Here is how you can solve it.

def externalize(model_obj):
  keys = model_obj._meta.get_all_field_names()
  data = {}
  for key in keys:
    if key == 'date_time':
      date_time_obj = getattr(model_obj, key)
      data[key] = date_time_obj.strftime("%A %d. %B %Y")
    else:
      data[key] = getattr(model_obj, key)
  return data

Not the answer you're looking for? Browse other questions tagged or ask your own question.