Author gvanrossum
Recipients amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger
Date 2013-06-21.14:49:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371826143.64.0.582581016441.issue18264@psf.upfronthosting.co.za>
In-reply-to
Content
The proposal to change json from using repr() to str() has unknown dangers.

I don't want the str() of IntEnum to return just the decimal string (e.g. "42"), since that breaks half of the usefulness of using the enum in the first place -- people will write print(x) and be confused.

Unfortunately the json module doesn't have a way to define *in the object* how to customize its serialization -- this is always done in the json encoder/decoder.  Maybe we can add something to the JSON encoder and decoder class that looks for a special method, e.g. __json_encode__ etc.?  (OR maybe this would be a use case for PEP 443?)
History
Date User Action Args
2013-06-21 14:49:03gvanrossumsetrecipients: + gvanrossum, barry, rhettinger, amaury.forgeotdarc, ncoghlan, pitrou, ezio.melotti, eli.bendersky, ethan.furman, eric.snow
2013-06-21 14:49:03gvanrossumsetmessageid: <1371826143.64.0.582581016441.issue18264@psf.upfronthosting.co.za>
2013-06-21 14:49:03gvanrossumlinkissue18264 messages
2013-06-21 14:49:03gvanrossumcreate