Message191631
| Author |
gvanrossum |
| Recipients |
amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger |
| Date |
2013年06月22日.02:49:12 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJ+y4oVGaO1zxKx3EYYhkQSFACsDUZvx9p6KhC5mXAcvDA@mail.gmail.com> |
| In-reply-to |
<CAF-Rda_5bTBz03OA_KNgV+udq5kVbpwgM9_g5sVivSY6hS6oQg@mail.gmail.com> |
| Content |
Change json to call int() first.
--Guido van Rossum (sent from Android phone)
On Jun 21, 2013 7:45 PM, "Eli Bendersky" <report@bugs.python.org> wrote:
>
> Eli Bendersky added the comment:
>
> 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
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue18264>
> _______________________________________
> |
|