Author eli.bendersky
Recipients amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger
Date 2013-06-22.02:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAF-Rda_5bTBz03OA_KNgV+udq5kVbpwgM9_g5sVivSY6hS6oQg@mail.gmail.com>
In-reply-to <20130621215901.5b83a09d@limelight.wooz.org>
Content
On Fri, Jun 21, 2013 at 6:59 PM, Barry A. Warsaw <report@bugs.python.org>wrote:

>
> Barry A. Warsaw added the comment:
>
> On Jun 22, 2013, at 01:08 AM, Nick Coghlan wrote:
>
> >Can I vote for something like "__builtin__" as the protocol, rather than
> >something entirely specific to serialisation? As in "return the most
> >appropriate builtin type with the same value"? Then a converter
> >("operator.builtin"?) could coerce builtin subclasses to their base
> classes
> >by default, rather than needing to implement the protocol on every type.
>
> Such a protocol needs a way to deserialize as well.  You can't necessarily
> assume (or shouldn't impose) that the __init__() can do that conversion.
>  In
> any case...
>
> >Such a design would need a PEP, of course.
>
> ...yes, definitely.

Practically speaking, what should be done to make enum play well with JSON
without writing new PEPs? I think we still want to convert those stdlib
constants to IntEnums...

Eli
History
Date User Action Args
2013-06-22 02:45:35eli.benderskysetrecipients: + eli.bendersky, gvanrossum, barry, rhettinger, amaury.forgeotdarc, ncoghlan, pitrou, ezio.melotti, ethan.furman, eric.snow
2013-06-22 02:45:35eli.benderskylinkissue18264 messages
2013-06-22 02:45:35eli.benderskycreate