Guido van Rossum added the comment:
Change json to call int() first.
--Guido van Rossum (sent from Android phone)
On Jun 21, 2013 7:45 PM, "Eli Bendersky" <rep...@bugs.python.org> wrote:
>
> Eli Bendersky added the comment:
>
> On Fri, Jun 21, 2013 at 6:59 PM, Barry A. Warsaw <rep...@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
>
> ----------
>
> _______________________________________
> Python tracker <rep...@bugs.python.org>
> <http://bugs.python.org/issue18264>
> _______________________________________
>
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue18264>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
