[Python-ideas] Python Object Notation (PyON)

Zaur Shibzoukhov szport at gmail.com
Thu Nov 6 09:08:33 CET 2008

2008/11/6 Josiah Carlson <josiah.carlson at gmail.com>:

> I guess I really don't understand the purpose of PyON.  Syntactically
> it doesn't fit between json and yaml.  It supports features that are
> more useful for a serialization language for RPC, etc., rather than
> configuration/inlining.  And it doesn't really offer a reverse of
> representation -> object without going through the standard Python
> parser and executing the result (which has security implications).
PyON dosn't use exec in order to reconstruct obbject.
It uses python parser for constructing AST and then builds object
using pickle-like protocol from AST.
I guess PyON could be used as standard reconstructable representation
of python objects.

> Again, json is very human readable/writable, is very close to literal
> Python syntax, and already has support in just about every language
> worth discussing (and Python offers a json loading module in the
> standard library).  Can you give me a good reason why someone would
> want to choose PyON over json in 6 months?
If someone need standard way for reconstructable representation
of almost every python object based on python syntax then PyON is a
possible choice (probably in near future).
Also maybe in the future someone will offer better solution for
reconstructable representation of
python objects based on python syntax.

Also I do not think that PyON should be used instead of JSON.

Best regards,

More information about the Python-ideas mailing list