Draft PEP on RSON configuration file format
in [Python]
|
Prev: [ANNC] pynguin-0.1 (python-based turtle graphics application)
Next: Detecting new removable drives in Linux
From: Patrick Maupin on 28 Feb 2010 21:09 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. I would love for it to be considered valuable enough to be a part of the standard library, but even if that does not come to pass, I would be very interested in feedback to help me polish the specification, and then possibly help for implementation and testing. The documentation is in rst PEP form, at: http://rson.googlecode.com/svn/trunk/doc/draftpep.txt Thanks and best regards, Pat
From: Paul Rubin on 28 Feb 2010 21:55 Patrick Maupin <pmaupin(a)gmail.com> writes: > I have started work on a new configuration file parser.... > The documentation is in rst PEP form, at:... Noooooooo.... not another... there are too many already. :-( -1
From: Steven D'Aprano on 28 Feb 2010 22:18 On Sun, 28 Feb 2010 20:09:30 -0600, Patrick Maupin wrote: > 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. Wait a minute... if JSON is too hard to edit, and RSON is a *superset* of JSON, that means by definition every JSON file is also a valid RSON file. Since JSON is too hard to manually edit, so is RSON. > I would love for it to be considered valuable enough to be a part of the > standard library, Come back when you actually have MANY users other than yourself using this is real-world projects. Until then, it is too early to even consider adding it the std library. Python comes with batteries included, but not experimental batteries that aren't even built yet, let alone proven that they work. -- Steven
From: John Nagle on 1 Mar 2010 01:39 Patrick Maupin wrote: > 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. You're not supposed to edit those formats manually. John Nagle
From: Chris Rebert on 1 Mar 2010 01:30
On Sun, Feb 28, 2010 at 10:39 PM, John Nagle <nagle(a)animats.com> wrote: > Patrick Maupin wrote: >> >> 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. > > Â You're not supposed to edit those formats manually. Huh? True for XML /perhaps/, but for the others I quite disagree. Perhaps you could explain your reasoning? Cheers, Chris -- http://blog.rebertia.com |