So, implementing __repr__() enables this...
> y=eval(repr(y))
But who need to generated python constructor calls? It isn't enforced, so a serializer library shouldn't trust it.
It just strikes me as an early idea that didn't pan out, but is everywhere.
compare this to say C#'s, ToString() and TryParse(), Format() etc... which are various interfaces that other parts of the standard library cold rely on and trust
♡ 0 ↻ 0