configobj-develop — Support and development of ConfigObj

Re: [Configobj-develop] validate 0.3.1 raises TypeError on Validator.get_default_value with default=None

[Michael F. <fuz...@vo...>]

Sebastian Wiesner wrote:
> Hi,
>
> http://paste.pocoo.org/show/29547/
>
> This rather nasty, as it affects ConfigObj quite severly: It simply breaks 
> validation, if the configspec contains any test with default value set to 
> None. 
>   

This should now be fixed in SVN. Due to the seriousness of the issue 
I'll try to do a new release ASAP.

Michael

> regards
> Sebastian Wiesner
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   

Re: [Configobj-develop] validate 0.3.1 raises TypeError on Validator.get_default_value with default=None

[Michael F. <fuz...@vo...>]

Sebastian Wiesner wrote:
> Hi,
>
> http://paste.pocoo.org/show/29547/
>
> This rather nasty, as it affects ConfigObj quite severly: It simply breaks 
> validation, if the configspec contains any test with default value set to 
> None. 
>
>   
Ok - sounds like it will be easy to fix. Thanks for the report.

Michael


> regards
> Sebastian Wiesner
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   

[Configobj-develop] validate 0.3.1 raises TypeError on Validator.get_default_value with default=None

[Sebastian W. <bas...@gm...>]

Hi,

http://paste.pocoo.org/show/29547/

This rather nasty, as it affects ConfigObj quite severly: It simply breaks 
validation, if the configspec contains any test with default value set to 
None. 

regards
Sebastian Wiesner

-- 
Freedom is always the freedom of dissenters.
                                      (Rosa Luxemburg)

Re: [Configobj-develop] ConfigObj Supporting toggles used in mysql configurations

[Michael F. <fuz...@vo...>]

Brian Jones wrote:
> Ok, so I took a quick break from reading the March stuff to look this
> over. I haven't read the *entire* thing, but I have a question about
> ConfigObj, and I hope I've read enough of the article that it's not
> too dumb a question :)
>   

It's definitely not a dumb question.

What you are saying is that the presence of:

x

Implies 'x = True'

This is fine - except it means changing the parser (which can be 
fiddly), making it an option, making it an option to specify how 'x = 
True' should be written back out (maybe both those could be a single 
option) and so on.

For config files *created* by ConfigObj I wouldn't want it to be the 
default but I am happy for ConfigObj to be compatible with a wider range 
of files created by other applications.

I'm afraid I have another rather pressing writing task at the moment - 
so I'm afraid the default response is 'patches welcomed'.

I'm forwarding this to the ConfigObj mailing list in case anyone else 
has an interest in implementing this...

Michael
http://www.manning.com/foord

> Given the very simple interface, and some of the complex things that
> ConfigObj does, I'm wondering how hard it would be to add support for
> "toggles" in a config file. In other words, single values on a line by
> themselves in a config file that, by their presence, signal the
> application to do (or not do) something specific.
>
> As an example, I actually needed this feature to write a mysql backup
> script that would parse the system's my.cnf file instead of having to
> edit a bunch of vars at the top of the script before use. However, the
> config file contains "toggle" config variables: if they exist in the
> file at all, they are basically read in by MySQL as "true", and it
> does what it needs to do. Here's a bit of the my.cnf file in question:
>
> [mysqld]
> server-id=2
> log-bin=mysql-binlog
> log-slave-updates
> relay-log=db2-relay-bin
> datadir=/var/lib/mysql
> tmpdir=/var/lib/mysql
> socket=/var/lib/mysql/mysql.sock
> enable-locking
> max_allowed_packet = 4M
> skip-name-resolve
> skip-host-cache
> skip-innodb
> back_log=128
> connect_timeout=10
> ft_min_word_len=3
> key_buffer_size=512M
> max_allowed_packet=1024M
> max_connections=200
> max_connect_errors=100
> myisam_sort_buffer_size=512M
>
> There's a lot of information implied by some of those floating, lonely
> values (and there are more that are available for use as well). If my
> application, for example, could do something like this:
>
> if not 'skip-innodb' in mysqlcnf:
>     do_innodb_backup()
>
> or, better:
>
> if not mysqlcnf['skip-innodb']
>     do_innodb_backup()
>
> So, I guess the short question is: can't ConfigObj just store these
> "toggle" values in a dictionary along with everything else, but since
> it doesn't have a value, just store the toggle value as the key, and
> the boolean True as the value?
>
> If this is all very neophyte-level banter, please forgive my
> ignorance. I don't profess to be a Python guru. That's why I created
> PyMag and hired tech editors :-P - but I do like Python, and would
> love to use ConfigObj for this particular project :-D
>
> Thanks for your work on this, and for working with us at PyMag!
> brian.
>
>
>
>
> On Thu, Feb 21, 2008 at 8:28 PM, Doug Hellmann <dou...@gm...> wrote:
>   
>> Thanks, Michael,
>>
>>  We're catching our breath from working on the March issue right now,
>>  but one of us will be looking at this shortly and will get back to you.
>>
>>  Doug
>>
>>  On Feb 21, 2008, at 3:34 PM, Michael Foord wrote:
>>
>>  > Hello guys,
>>  >
>>  > Attached is the first draft of my ConfigObj article. I have ignored
>>  > formatting issues so far...
>>     
>
>   

[Configobj-develop] Matplotlib

[Michael F. <fuz...@vo...>]

Looks like matplotlib is using ConfigObj now as well!

http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/lib/

Michael

Re: [Configobj-develop] New Release

[Arve K. <arv...@gm...>]

On Feb 5, 2008 7:22 PM, Michael Foord <fuz...@vo...> wrote:
> Arve Knudsen wrote:
> > Great!
> >
>
> Hmmm - except I've just seen a bug report on sourceforge that validate
> doesn't work with unicode configspecs. I've now fixed it in SVN and need
> to decide whether to update the release which I am half way through.
>
> I will probably update, but it is annoying as it is so much work for a
> tiny fix.

I can relate to that, but know that your work is appreciated.

Arve

> Michael
>
>
> > Arve
> >
> > On Feb 5, 2008 12:40 AM, Michael Foord <fuz...@vo...> wrote:
> >
> >> Hello all,
> >>
> >> I'm pushing out a new release. It is already up on the website but I
> >> need to generate eggs on a Linux box before I can do an announcement.
> >>
> >> Michael
> >>
> >> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Microsoft
> >> Defy all challenges. Microsoft(R) Visual Studio 2008.
> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >> _______________________________________________
> >> Configobj-develop mailing list
> >> Con...@li...
> >> https://lists.sourceforge.net/lists/listinfo/configobj-develop
> >>
> >>
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Configobj-develop mailing list
> > Con...@li...
> > https://lists.sourceforge.net/lists/listinfo/configobj-develop
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>

Re: [Configobj-develop] New Release

[Michael F. <fuz...@vo...>]

Arve Knudsen wrote:
> Great!
>   

Hmmm - except I've just seen a bug report on sourceforge that validate 
doesn't work with unicode configspecs. I've now fixed it in SVN and need 
to decide whether to update the release which I am half way through.

I will probably update, but it is annoying as it is so much work for a 
tiny fix.

Michael

> Arve
>
> On Feb 5, 2008 12:40 AM, Michael Foord <fuz...@vo...> wrote:
>   
>> Hello all,
>>
>> I'm pushing out a new release. It is already up on the website but I
>> need to generate eggs on a Linux box before I can do an announcement.
>>
>> Michael
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Configobj-develop mailing list
>> Con...@li...
>> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>>
>>     
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>
>   

Re: [Configobj-develop] New Release

[Arve K. <arv...@gm...>]

Great!

Arve

On Feb 5, 2008 12:40 AM, Michael Foord <fuz...@vo...> wrote:
> Hello all,
>
> I'm pushing out a new release. It is already up on the website but I
> need to generate eggs on a Linux box before I can do an announcement.
>
> Michael
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>

[Configobj-develop] New Release

[Michael F. <fuz...@vo...>]

Hello all,

I'm pushing out a new release. It is already up on the website but I 
need to generate eggs on a Linux box before I can do an announcement.

Michael

Re: [Configobj-develop] Testing latest version

[Michael F. <fuz...@vo...>]

Hello Jeffrey,

I'd really appreciate you testing reload. The easiest way to get the new
version is to download it from this blog entry:

http://www.voidspace.org.uk/python/weblog/arch_d7_2008_01_26.shtml#e928

If the CVS you are referring to is the sourceforge one, I don't use it. The
SVN repository is hosted by Python Hosting (Webfaction):

http://svn.pythonutils.python-hosting.com/trunk/pythonutils/

There haven't been any commits since the release candidate I posted to my
blog though.

All the best,

Michael Foord

On 29/01/2008, Jeffrey Barish <jef...@ea...> wrote:
>
> I thought that I should try the latest version with the new reload command
> since it was I who requested that it be added.  However, I am having
> trouble
> finding the new version.  I don't know much about CVS, so most likely I am
> doing something stupid, but when I follow the directions under "Anonymous
> CVS
> Access", I see nothing and when I follow the link to "web-based CVS
> repository viewer" I again see nothing.  How do I get the latest version?
> --
> Jeffrey Barish
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>



-- 
http://www.manning.com/foord
http://www.voidspace.org.uk
http://www.ironpython.info

[Configobj-develop] Testing latest version

[Jeffrey B. <jef...@ea...>]

I thought that I should try the latest version with the new reload command 
since it was I who requested that it be added.  However, I am having trouble 
finding the new version.  I don't know much about CVS, so most likely I am 
doing something stupid, but when I follow the directions under "Anonymous CVS 
Access", I see nothing and when I follow the link to "web-based CVS 
repository viewer" I again see nothing.  How do I get the latest version?
-- 
Jeffrey Barish

[Configobj-develop] 'restore_default' and 'restore_defaults' methods added

[Michael F. <fuz...@vo...>]

Hello all,

'restore_default' and 'restore_defaults' methods added. Release 
candidate announcement to follow.

Michael

[Configobj-develop] Steps towards 'restore_default'

[Michael F. <fuz...@vo...>]

Hello all,

I've been working on integrating the patch supplied by Arve that would 
add a 'restore_default' method to ConfigObj sections.

Although it was a great reference implementation, I was unhappy with the 
performance hit of parsing each check an extra time to retrieve the 
default value. Instead I've implemented it with caching of parsed 
checks. This should provide a general performance improvement for most 
configspec handling.

This is now in subversion. The next step is to implement 
'restore_default' on 'Section' (and probably a 'restore_defaults' as well).

The full changelog for validate currently stands at:

Improved performance with a parse cache.

    New ``get_default_value`` method. Given a check it returns the default
    value (converted to the correct type) or raises a ``KeyError`` if the
    check doesn't specify a default.

    Bugfix: A quoted 'None' as a default value is no longer treated as None,
    but as the string 'None'.

    Bugfix: we weren't unquoting keyword arguments of length two, so an
    empty string didn't work as a default.

    Bugfix: Strings no longer pass the 'is_list' check. Additionally, the
    list checks always return lists.
   
    Added 'tuple' check and corresponding 'is_tuple' function (which 
always returns a tuple).

    A couple of documentation bug fixes.

    Removed CHANGELOG from module.


I've made one further change to  ConfigObj:

    ConfigObj will no longer attempt to import the ``validate`` module, 
until/unless
    you call ``ConfigObj.validate`` with ``preserve_errors=True``. This 
makes it
    faster to import.

All the best,

Michael Foord
http://www.manning.com/foord

Re: [Configobj-develop] reload and reset committed - what about istrue, encode and decode?

[Fuzzyman <fuz...@vo...>]

Nicola Larosa wrote:

>Fuzzyman wrote:
>  
>
>>(plus a newlines bugfix if Nicola ever sends it)
>>    
>>
>
>I sent a bug report yesterday, did you see it? It's a bit buried in the
>"ConfigObj changes" thread.
>  
>

Ha! I missed it somehow (?). By coincidence it is the same bug that I 
spotted and fixed yesterday - so it is already fixed in SVN. :-)

Michael

Re: [Configobj-develop] reload and reset committed - what about istrue, encode and decode?

[Nicola L. <ni...@te...>]

Fuzzyman wrote:
> (plus a newlines bugfix if Nicola ever sends it)

I sent a bug report yesterday, did you see it? It's a bit buried in the
"ConfigObj changes" thread.

-- 
Nicola Larosa - http://www.tekNico.net/

Don't use Madonna as a role model if who you *really* relate to is Joni
Mitchell. Or vice versa. Don't mutilate your foot, trying to squeeze it
into Cinderella's slipper. I've tried to do some of that myself, but
nowadays there's no doubt in my mind: I'm one of the ugly sisters.
And *proud* of it.  -- Joe Jackson, A Cure for Gravity, 1999

[Configobj-develop] reload and reset committed - what about istrue, encode and decode?

[Fuzzyman <fuz...@vo...>]

Hello everyone,

I am just committing some new changes to ConfigObj.

These include some stylistic changes for readability, plus two new methods:

* reset - restore a ConfigObj instance to a freshly initialised state
* reload - reload the current config file

reload is the more important change, with the following notes:

* It can only succeed if the config file was originally loaded from the
filesystem - i.e. the filename attribute is set to a string. Otherwise a
'ReloadError' (a new exception that is a subclass of IOError) will be
raised.
* The ConfigObj is first cleared and then reloaded - so any direct
references to sections will be orphaned by reload
* ConfigObj construction now holds a reference to the configspec in
whatever form you originally pass it in. It is reused by 'reload', so if
you pass in the configspec as a filename then it will also be reloaded.
* reload *doesn't* reset options to their original state (like
list_values, unrepr, raise_errors, create_empty etc) - it uses the
current options. The exception are attributes like BOM and newlines that
are set in the process of parsing the file.

Currently both reload and write are sensitive to the current working
directory. If you pass in a relative filename and then change the
current directory then both reload and write will 'do the wrong thing'.
I wonder whether to change this, but there is a backwards compatibility
issue (people could easily be relying on the current behaviour).

Additionally, istrue, encode and decode have been marked as deprecated
for some time. The new release (when it comes) will be version 4.5. It
would be nice to remove these - but on the other hand they do little
harm just sitting there. Any thoughts?

reload is tested, but ConfigObj has so many private members
(particularly when dealing with configspecs) that it is hard to be 100%
certain that all angles are covered. If anyone is able to test this 'in
the field' it would be appreciated.

The full changelog from 4.4.0 to current head is:

ConfigObj will now guarantee that files will be written terminated with a
newline.

BUGFIX: Proper quoting of keys, values and list values that contain hashes
(when writing).  When ``list_values=False``, values containing hashes are
triple quoted.

Added the ``reload`` method. This reloads a ConfigObj from file. If the
filename
attribute is not set then a ``ReloadError`` (a new exception inheriting from
``IOError``) is raised.

BUGFIX: Files are read in in 'rb' mode, so that non native line endings
will be
preserved.

Minor efficiency improvement in ``unrepr`` mode.

Added missing docstrings for overridden dictionary methods.

Added the ``reset`` method. This restores a ConfigObj to a freshly
created state.

(Plus the changes to the validate module discussed previously.)

Adding reload didn't require much code, but it meant revisiting a lot of
code I haven't touched for quite a while. The code quality isn't bad,
but there is too much of it! A lot of the methods are very long and only
a fairly large refactoring can sort that out. I did a bit of (necessary)
refactoring adding reload and hopefully good changes can be made
incrementally. Just the 'restore_defaults' patch to add now (plus a
newlines bugfix if Nicola ever sends it) before I declare a release
candidate. Test first with doctest is painful!

All the best,

Michael Foord

Re: [Configobj-develop] ConfigObj Changes

[Nicola L. <ni...@te...>]

> Nicola Larosa wrote:
>> I've been sitting on a bug report about newlines on Windows for some time
>> (sorry). It's in Italian, I'll translate it and send it here soon.

Michael Foord wrote:
> Ok - cool. But how many problems with newlines can there *be*? :-)

That one, I'm not qualified to answer. ;-) Bug report follows.

---

When creating a ConfigObj, there's some code that tries to detect what
kind of newline is used in the input file, in order to use the same kind
when the ConfigObj is saved.
Now, in the "write" method the output file is open as binary, for
encoding reasons:

Lines from 1848 to 1050:

h = open(self.filename, 'wb')
h.write(output)
h.close()

and the lines are added to the output buffer appending to each one the
self.newlines character, the one detected in the constructor (one among
"\n", "\r" and "\r\n").

The problem is that in all systems the output newline character in
self.newlines will always be "\n", because the input file "infile",
passed in the constructor, is open in text mode, therefore the newline
characters it contains will already have been converted to "\n":

Lines 1022 and 1023:

if os.path.isfile(infile):
    infile = open(infile).read() or []

So, I changed those two lines to:

if os.path.isfile(infile):
    infile = open(infile,"rb").read() or []

That way, the input file too is open in binary mode, and the newline
character put into self.newlines is the actually used one.

All of that because on windows [lowercased in the original ;-) ], when a
ConfigObj is written to file, the newline characters were shown as "\n",
that in notepad are seen as annoying little boxes. :-)

---

I hope it's useful.

-- 
Nicola Larosa - http://www.tekNico.net/

I was a pilgrim, dedicated to the service of something larger than
myself, something that transcended the mundane material world,
something that could still fill me with awe. Music was my Christ on
the cross, my Wailing Wall, my Mecca. A universe in which music
existed could not be evil. -- Joe Jackson, A Cure for Gravity, 1999

Re: [Configobj-develop] [python] Re: Validate fixes in SVN

[Frederik E. <fre...@we...>]

Am Mittwoch, den 16.01.2008, 22:48 +0000 schrieb Michael Foord:
> Frederik Elwert wrote:
> The point is, if you have the keywords as a dictionary you can always do:
> 
> c = ConfigObj(filename, **options)
> 
> I think the dictionary of parameters is a hangover from ConfigObj 3, 
> back when I didn't know you could unpack dictionaries like that. :-)

Oh, sure, then it's all right! :-)

Frederik

Re: [Configobj-develop] [python] Re: Validate fixes in SVN

[Arve K. <arv...@gm...>]

On Jan 16, 2008 11:21 PM, Michael Foord <fuz...@vo...> wrote:

> Arve Knudsen wrote:
> > Superb. Glad to see the list conversion bug is fixed.
>
> Cool, it would be great if you could test the version in SVN to see if
> it really fixes your problems (and doesn't introduce new ones).


I've tested, and no problems detected so far (strings are no longer accepted
for lists).

Arve


>
> Next I'm looking at adding 'reset', 'reload' and 'restore_defaults'
> (your patch) to ConfigObj. If I add these methods then the new release
> will be version 4.5.0 I guess.
>
> I'd lake to make some other changes to the API - but as these break
> backwards compatibility they will have to wait some unspecified length
> of time for a version 5:
>
> 'write' should return a string rather than a list of strings if there is
> no filename.
> The options dictionary parameter in the constructor doesn't really make
> sense.
>
> Michael
> http://www.manning.com/foord
>
>
> >
> > Thanks,
> > Arve
> >
> > On Jan 16, 2008 3:07 PM, Michael Foord <fuz...@vo...
> > <mailto:fuz...@vo...>> wrote:
> >
> >     Hello all,
> >
> >     The following changes to the validate module are now in SVN:
> >
> >     A couple of documentation bug fixes.
> >
> >     Removed CHANGELOG from module.
> >
> >     Bugfix: we weren't unquoting keyword arguments of length two, so an
> >     empty string didn't work as a default.
> >
> >     Bugfix: Strings no longer pass the 'is_list' check. Additionally,
> the
> >     list checks always return lists.
> >
> >     Added 'tuple' check and corresponding 'is_tuple' function (which
> >     always
> >     returns a tuple).
> >
> >     All the best,
> >
> >
> >     Michael
> >
> >
> -------------------------------------------------------------------------
> >
> >     This SF.net email is sponsored by: Microsoft
> >     Defy all challenges. Microsoft(R) Visual Studio 2008.
> >     http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >     <http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/>
> >     _______________________________________________
> >     Configobj-develop mailing list
> >     Con...@li...
> >     <mailto:Con...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/configobj-develop
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Configobj-develop mailing list
> > Con...@li...
> > https://lists.sourceforge.net/lists/listinfo/configobj-develop
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>

Re: [Configobj-develop] [python] Re: Validate fixes in SVN

[Michael F. <fuz...@vo...>]

Frederik Elwert wrote:
> Am Mittwoch, den 16.01.2008, 22:21 +0000 schrieb Michael Foord:
>   
>> The options dictionary parameter in the constructor doesn't really make 
>> sense.
>>     
>
> Doesn't it? I use it because I use the constructor in several places,
> and this way I only have to change options once. But maybe this is a
> minority position.
>
>   


The point is, if you have the keywords as a dictionary you can always do:

c = ConfigObj(filename, **options)

I think the dictionary of parameters is a hangover from ConfigObj 3, 
back when I didn't know you could unpack dictionaries like that. :-)

Michael

> Frederik
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>
>   

Re: [Configobj-develop] [python] Re: Validate fixes in SVN

[Frederik E. <fre...@we...>]

Am Mittwoch, den 16.01.2008, 22:21 +0000 schrieb Michael Foord:
> The options dictionary parameter in the constructor doesn't really make 
> sense.

Doesn't it? I use it because I use the constructor in several places,
and this way I only have to change options once. But maybe this is a
minority position.

Frederik

Re: [Configobj-develop] [python] Re: Validate fixes in SVN

[Michael F. <fuz...@vo...>]

Arve Knudsen wrote:
> Superb. Glad to see the list conversion bug is fixed.

Cool, it would be great if you could test the version in SVN to see if 
it really fixes your problems (and doesn't introduce new ones).

Next I'm looking at adding 'reset', 'reload' and 'restore_defaults' 
(your patch) to ConfigObj. If I add these methods then the new release 
will be version 4.5.0 I guess.

I'd lake to make some other changes to the API - but as these break 
backwards compatibility they will have to wait some unspecified length 
of time for a version 5:

'write' should return a string rather than a list of strings if there is 
no filename.
The options dictionary parameter in the constructor doesn't really make 
sense.

Michael
http://www.manning.com/foord


>
> Thanks,
> Arve
>
> On Jan 16, 2008 3:07 PM, Michael Foord <fuz...@vo... 
> <mailto:fuz...@vo...>> wrote:
>
>     Hello all,
>
>     The following changes to the validate module are now in SVN:
>
>     A couple of documentation bug fixes.
>
>     Removed CHANGELOG from module.
>
>     Bugfix: we weren't unquoting keyword arguments of length two, so an
>     empty string didn't work as a default.
>
>     Bugfix: Strings no longer pass the 'is_list' check. Additionally, the
>     list checks always return lists.
>
>     Added 'tuple' check and corresponding 'is_tuple' function (which
>     always
>     returns a tuple).
>
>     All the best,
>
>
>     Michael
>
>     -------------------------------------------------------------------------
>
>     This SF.net email is sponsored by: Microsoft
>     Defy all challenges. Microsoft(R) Visual Studio 2008.
>     http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>     <http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/>
>     _______________________________________________
>     Configobj-develop mailing list
>     Con...@li...
>     <mailto:Con...@li...>
>     https://lists.sourceforge.net/lists/listinfo/configobj-develop
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   

Re: [Configobj-develop] Validate fixes in SVN

[Arve K. <arv...@gm...>]

Superb. Glad to see the list conversion bug is fixed.

Thanks,
Arve

On Jan 16, 2008 3:07 PM, Michael Foord <fuz...@vo...> wrote:

> Hello all,
>
> The following changes to the validate module are now in SVN:
>
> A couple of documentation bug fixes.
>
> Removed CHANGELOG from module.
>
> Bugfix: we weren't unquoting keyword arguments of length two, so an
> empty string didn't work as a default.
>
> Bugfix: Strings no longer pass the 'is_list' check. Additionally, the
> list checks always return lists.
>
> Added 'tuple' check and corresponding 'is_tuple' function (which always
> returns a tuple).
>
> All the best,
>
>
> Michael
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>

[Configobj-develop] Validate fixes in SVN

[Michael F. <fuz...@vo...>]

Hello all,

The following changes to the validate module are now in SVN:

A couple of documentation bug fixes.

Removed CHANGELOG from module.

Bugfix: we weren't unquoting keyword arguments of length two, so an
empty string didn't work as a default.

Bugfix: Strings no longer pass the 'is_list' check. Additionally, the
list checks always return lists.

Added 'tuple' check and corresponding 'is_tuple' function (which always 
returns a tuple).

All the best,


Michael

Re: [Configobj-develop] Validate and default=""

[Michael F. <fuz...@vo...>]

Michael Foord wrote:
> Hello all,
>
> There was a reported bug that using default="" with validate was broken, 
> so I will be looking at that.
>   

We weren't unquoting strings of length two... :-)

Fixed.

Michael

> There are a lot of fairly chunky regular expressions in validate...
>
>
> Michael
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>
>