Here’s how I was able to use the custom encoder. Not sure if it is the best way though…

http://blog.adaptivesoftware.biz/2009/08/custom-json-encoder-in-django.html

Thanks for the response. I tried passing my custom encoder with the cls parameter as suggested, but I got an error msg:

dump() got multiple values for keyword argument ‘cls’

I will figure out the correct way to do this and post it back here.

Thanks for taking the time to help me.

–
Regards
Parag

I assume from your terminology that you’re working with Django. It looks like at the bottom of the django documentation on serialization it has some clues. i havent dont this myself, but if your custom encoder is called MyEncoder, i would try something like:

json_serializer = serializers.get_serializer(”json”)()
json_serializer.serialize(queryset, cls=MyEncoder, stream=response)

‘cls’ is the argument you use to pass the custm encoder to the json.dump() function as well (that was originally in my post, but i think that paragraph was eaten by the pre-formatter– argh.

Good luck!

However, I have a question. How do you tie MyEncoder in the serialization flow. So for example if my serialization code is such:

res = serializers.serialize(”json”, questions)

Where questions is a QuerySet, and I want to use a custom encoder for encoding to be able to encode DateTime objects in a different way then the default JSONEncoder. How do I ensure that the above call uses the custom encoder instead of the default one.

–
Thanks
Parag