Message191628
| Author |
barry |
| Recipients |
amaury.forgeotdarc, barry, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, gvanrossum, ncoghlan, pitrou, rhettinger |
| Date |
2013年06月22日.01:59:04 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20130621215901.5b83a09d@limelight.wooz.org> |
| In-reply-to |
<CADiSq7dtDYqpYyvs7X1+D+cSsNzUny2i_u=qCqXuoc=cftKANA@mail.gmail.com> |
| Content |
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. |
|