On Mon, Mar 1, 2010 at 3:02 AM, Daniel Fetchinson wrote:
> Quick question: if JSON is too hard to manually edit, how can RSON be
> any easier when it is a *superset* of JSON?
>
Well, Python is essentially a superset of JSON, with string escape handling
being ever so slightly different, and usin
> Finding .ini configuration files too limiting, JSON and XML to hard to
> manually edit
[snip]
> I call the new format RSON (for "Readable Serial Object Notation"),
> and it is designed to be a superset of JSON.
Quick question: if JSON is too hard to manually edit, how can RSON be
any easier wh
On Sun, Feb 28, 2010 at 7:51 PM, Antoine Pitrou wrote:
> Well, a constructive approach would involve approaching projects
> which have devised their own formats, so as to know what kind of
> unified format they would be likely to accept (or not).
Trying to poll "selected projects which have confi
Le Sun, 28 Feb 2010 19:46:30 -0600,
Patrick Maupin a écrit :
>
> I suppose I have that sort of reaction about areas I am not interested
> in, as well, but currently I am deeply interested in configuration
> files due to my circumstances. In any case, the observation that
> there are already seve
On Sun, Feb 28, 2010 at 7:39 PM, Antoine Pitrou wrote:
> In this case it is *at best* python-ideas material, or even
> preferably comp.lang.python.
I was thinking about comp.lang.python at some point, but thought I
would try here first.
> Just for the record, my only reaction when giving the PE
Le Sun, 28 Feb 2010 18:59:16 -0600,
Patrick Maupin a écrit :
>
> So, I do not mind the code sitting outside the standard library, and
> the PEP not reaching "Final" for several years, but I do believe that
> the PEP process is itself a really good way to build a better
> mousetrap by consensus.
On Sun, Feb 28, 2010 at 6:29 PM, Benjamin Peterson wrote:
> In that case, it should live in the user space for several years. If
> the community decides that it is an excellent format, then it should
> be considered for inclusion in the stand library.
Agreed.
However, there are too many things w
2010/2/28 Patrick Maupin :
> All:
>
> Finding .ini configuration files too limiting, JSON and XML to hard to
> manually edit, and YAML too complex to parse quickly, I have started
> work on a new configuration file parser.
In that case, it should live in the user space for several years. If
the co
All:
Finding .ini configuration files too limiting, JSON and XML to hard to
manually edit, and YAML too complex to parse quickly, I have started
work on a new configuration file parser.
I call the new format RSON (for "Readable Serial Object Notation"),
and it is designed to be a superset of JSON
