Message191626
| Author |
gvanrossum |
| Recipients |
amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger |
| Date |
2013年06月22日.01:17:52 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAP7+vJ+G61akPGECTmwMchf+LhLWOkyZKjBeV=tP2O3yW-F40A@mail.gmail.com> |
| In-reply-to |
<CADiSq7dtDYqpYyvs7X1+D+cSsNzUny2i_u=qCqXuoc=cftKANA@mail.gmail.com> |
| Content |
Hm. Then I prefer just calling the appropriate builtin, e.g. int().
--Guido van Rossum (sent from Android phone)
On Jun 21, 2013 6:08 PM, "Nick Coghlan" <report@bugs.python.org> wrote:
>
> Nick Coghlan added the comment:
>
> 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 design would need a PEP, of course.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue18264>
> _______________________________________
> |
|