Hi Daniel,
Working on unrelated code, I found that the iniparse module, which we
ship on our F9 and F11 OSs, knows the ordering of the sections.
from iniparse import INIConfig
import os
c = INIConfig(open(os.path.expanduser('~')+'/.sugar/default/config'))
list(c) # gives you the
2009/11/4 Martin Langhoff martin.langh...@gmail.com:
Hi Daniel,
Working on unrelated code, I found that the iniparse module, which we
ship on our F9 and F11 OSs, knows the ordering of the sections.
Cool, indeed, their site makes it pretty clear that preserving order
is a feature.
Daniel
2009/10/27 Martin Langhoff martin.langh...@gmail.com:
Right... makes sense. I am a bit intrigued with the custom config file
parser / writer (that is 3x the sloc of the whole xs-activation ;-) ).
It's not really a custom config file parser. It's a trivial change to
Python's own ConfigParser
On Thu, Oct 29, 2009 at 5:09 PM, Daniel Drake d...@laptop.org wrote:
I don't understand this question. My patch only adds it for
xs-activation purposes.
It is about avoiding maintaining a bespoke lib. If you say it is a
variant on a python standard lib, do you think we can subclass it? Or
is
2009/10/30 Martin Langhoff martin.langh...@gmail.com:
It is about avoiding maintaining a bespoke lib. If you say it is a
variant on a python standard lib, do you think we can subclass it? Or
is there a reason not to?
Yeah it can probably be subclassed.
It is needed up until Python 3.0,
On Sun, Oct 25, 2009 at 7:09 AM, Daniel Drake d...@laptop.org wrote:
Here's a patch that makes xs-activation server OS update information
based on what it has available in xs-rsync.
I like it -- thanks! It was in my TO DO notes with the earlier
xs-activation work, and ended up cutting it.
I
