configobj-develop — Support and development of ConfigObj

Re: [Configobj-develop] Validating with __many__...

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

Marc Tompkins wrote:
> Hi all -
>
> I hope this is not a horribly stupid question...

Hello Marc,

Your problem only occurs if 'copy=True' is set in the call to validate. 
This implies to me that it is a real bug.

I'm looking at it now.

Michael Foord

>
> I'm setting up my configspec thusly:
>  
>
>         tmpStr = """[Current]
>         npiXMLFile = string(default="npiMap.XML")
>         InHist = string_list(default=None)
>         OutHist = string_list(default=None)
>         Submitter = string(default=None)
>         Carrier = string(default=None)
>         MainSize = tuple()
>         MainPos = tuple()
>         SummarySize = tuple()
>         SummaryPos = tuple()
>         ConfirmSuccess = boolean(default=True)
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         [JobProfiles]
>         [[__many__]]
>         Submitter = string(default=" ")
>         Carrier = string(default=" ")
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         InFile = string(default="")
>         OutFile = string(default="")
>         """
>         cfgSpec = StringIO.StringIO(tmpStr)
>         cfgFile = ConfigObj(cfgFileName,
>                     configspec=cfgSpec, raise_errors=True,
>     write_empty_values = True,
>                     create_empty=True, indent_type='    ', list_values
>     = True)
>         vtor = Validator()
>
>
> and validating it thusly:
>
>         test = cfgFile.validate(vtor, copy=True)
>         cfgFile.write()
>
>
> My actual ini file looks like so:
>
>     [Current]
>         npiXMLFile = file:///E:/ultrahld/npiMap.xml
>         Submitter = 1234567
>         Carrier = ColoradoMedicare
>         ConfirmSuccess = True
>         KeepLicense = False
>         KeepInsID = False
>         KeepTaxID = True
>         KeepUxIN = False
>         KeepFacID = False
>         UseSecID = True
>         FixSSN = True
>         DNtoDQ = False
>         InHist = E:\ultrahld\MCARE06.837, E:\ultrahld\MCARE04.837,
>     E:\bbs\out.837
>         OutHist = E:\bbs\out.837, E:\bbs\MCAL03.NPI
>         CvtCarrier = True
>     [JobProfiles]
>         [[Bogus]]
>             Submitter = 8675309
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE04.837
>             OutFile = E:\bbs\out.837
>         [[ReallyBogus]]
>             Submitter = 345678
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE03.837
>             OutFile = E:\bbs\out.837
>
>
> If I cut the file short after [JobProfiles], all is well, but if I 
> include [[Bogus]] or [[ReallyBogus]] the validation blows up with the 
> following:
> Traceback (most recent call last):
>
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 538, in <module>
>     main()
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 530, in main
>     test = Global.cfgFile.validate(Global.vtor, copy=True)
>      File "c:\python25\lib\site-packages\configobj.py", line 2301, in
>     validate
>     copy=copy, section=section[entry])
>      File "c:\python25\lib\site-packages\configobj.py", line 2297, in
>     validate
>     section.comments[entry] = section._cs_section_comments[entry]
>     KeyError: 'Bogus'
>     Script terminated.
>
>
> I was poking around adding pprint() statements in configobj.py, and 
> the problem seems to be that when "__many__" occurs in the configspec, 
> no entries are created in section._cs_section_comments - which of 
> course they wouldn't be, because we don't know what the subsection 
> names are yet.
>
> I'm not actually using comments, and probably never will, so I suppose 
> I could just rip out all of that... but there must be a better way, 
> and I can't possibly be the only one who's run into this.  However, I 
> haven't seen it mentioned in the list archives, so I suspect I'm doing 
> something wrong.  What should I do?
>
> Windows XP Pro SP3
> Python 2.5.1
> wxPython 2.8.7.1 <http://2.8.7.1>
> ConfigObj 4
>
> -- 
> www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
http://www.resolverhacks.net/

Re: [Configobj-develop] Validating with __many__...

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

Hello Marc,

I'll have to look at this - I can't see the problem and it may be a bug.

Michael

Marc Tompkins wrote:
> Hi all -
>
> I hope this is not a horribly stupid question...
>
> I'm setting up my configspec thusly:
>  
>
>         tmpStr = """[Current]
>         npiXMLFile = string(default="npiMap.XML")
>         InHist = string_list(default=None)
>         OutHist = string_list(default=None)
>         Submitter = string(default=None)
>         Carrier = string(default=None)
>         MainSize = tuple()
>         MainPos = tuple()
>         SummarySize = tuple()
>         SummaryPos = tuple()
>         ConfirmSuccess = boolean(default=True)
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         [JobProfiles]
>         [[__many__]]
>         Submitter = string(default=" ")
>         Carrier = string(default=" ")
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         InFile = string(default="")
>         OutFile = string(default="")
>         """
>         cfgSpec = StringIO.StringIO(tmpStr)
>         cfgFile = ConfigObj(cfgFileName,
>                     configspec=cfgSpec, raise_errors=True,
>     write_empty_values = True,
>                     create_empty=True, indent_type='    ', list_values
>     = True)
>         vtor = Validator()
>
>
> and validating it thusly:
>
>         test = cfgFile.validate(vtor, copy=True)
>         cfgFile.write()
>
>
> My actual ini file looks like so:
>
>     [Current]
>         npiXMLFile = file:///E:/ultrahld/npiMap.xml
>         Submitter = 1234567
>         Carrier = ColoradoMedicare
>         ConfirmSuccess = True
>         KeepLicense = False
>         KeepInsID = False
>         KeepTaxID = True
>         KeepUxIN = False
>         KeepFacID = False
>         UseSecID = True
>         FixSSN = True
>         DNtoDQ = False
>         InHist = E:\ultrahld\MCARE06.837, E:\ultrahld\MCARE04.837,
>     E:\bbs\out.837
>         OutHist = E:\bbs\out.837, E:\bbs\MCAL03.NPI
>         CvtCarrier = True
>     [JobProfiles]
>         [[Bogus]]
>             Submitter = 8675309
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE04.837
>             OutFile = E:\bbs\out.837
>         [[ReallyBogus]]
>             Submitter = 345678
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE03.837
>             OutFile = E:\bbs\out.837
>
>
> If I cut the file short after [JobProfiles], all is well, but if I 
> include [[Bogus]] or [[ReallyBogus]] the validation blows up with the 
> following:
> Traceback (most recent call last):
>
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 538, in <module>
>     main()
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 530, in main
>     test = Global.cfgFile.validate(Global.vtor, copy=True)
>      File "c:\python25\lib\site-packages\configobj.py", line 2301, in
>     validate
>     copy=copy, section=section[entry])
>      File "c:\python25\lib\site-packages\configobj.py", line 2297, in
>     validate
>     section.comments[entry] = section._cs_section_comments[entry]
>     KeyError: 'Bogus'
>     Script terminated.
>
>
> I was poking around adding pprint() statements in configobj.py, and 
> the problem seems to be that when "__many__" occurs in the configspec, 
> no entries are created in section._cs_section_comments - which of 
> course they wouldn't be, because we don't know what the subsection 
> names are yet.
>
> I'm not actually using comments, and probably never will, so I suppose 
> I could just rip out all of that... but there must be a better way, 
> and I can't possibly be the only one who's run into this.  However, I 
> haven't seen it mentioned in the list archives, so I suspect I'm doing 
> something wrong.  What should I do?
>
> Windows XP Pro SP3
> Python 2.5.1
> wxPython 2.8.7.1 <http://2.8.7.1>
> ConfigObj 4
>
> -- 
> www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   


-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/

Re: [Configobj-develop] Validating with __many__...

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

Hello Marc,

I'll have to look at this - I can't see the problem and it may be a bug.

Michael

Marc Tompkins wrote:
> Hi all -
>
> I hope this is not a horribly stupid question...
>
> I'm setting up my configspec thusly:
>  
>
>         tmpStr = """[Current]
>         npiXMLFile = string(default="npiMap.XML")
>         InHist = string_list(default=None)
>         OutHist = string_list(default=None)
>         Submitter = string(default=None)
>         Carrier = string(default=None)
>         MainSize = tuple()
>         MainPos = tuple()
>         SummarySize = tuple()
>         SummaryPos = tuple()
>         ConfirmSuccess = boolean(default=True)
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         [JobProfiles]
>         [[__many__]]
>         Submitter = string(default=" ")
>         Carrier = string(default=" ")
>         CvtCarrier = boolean(default=False)
>         KeepLicense = boolean(default=False)
>         KeepInsID = boolean(default=False)
>         KeepTaxID = boolean(default=True)
>         KeepUxIN = boolean(default=True)
>         KeepFacID = boolean(default=False)
>         UseSecID = boolean(default=False)
>         FixSSN = boolean(default=True)
>         DNtoDQ = boolean(default=False)
>         InFile = string(default="")
>         OutFile = string(default="")
>         """
>         cfgSpec = StringIO.StringIO(tmpStr)
>         cfgFile = ConfigObj(cfgFileName,
>                     configspec=cfgSpec, raise_errors=True,
>     write_empty_values = True,
>                     create_empty=True, indent_type='    ', list_values
>     = True)
>         vtor = Validator()
>
>
> and validating it thusly:
>
>         test = cfgFile.validate(vtor, copy=True)
>         cfgFile.write()
>
>
> My actual ini file looks like so:
>
>     [Current]
>         npiXMLFile = file:///E:/ultrahld/npiMap.xml
>         Submitter = 1234567
>         Carrier = ColoradoMedicare
>         ConfirmSuccess = True
>         KeepLicense = False
>         KeepInsID = False
>         KeepTaxID = True
>         KeepUxIN = False
>         KeepFacID = False
>         UseSecID = True
>         FixSSN = True
>         DNtoDQ = False
>         InHist = E:\ultrahld\MCARE06.837, E:\ultrahld\MCARE04.837,
>     E:\bbs\out.837
>         OutHist = E:\bbs\out.837, E:\bbs\MCAL03.NPI
>         CvtCarrier = True
>     [JobProfiles]
>         [[Bogus]]
>             Submitter = 8675309
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE04.837
>             OutFile = E:\bbs\out.837
>         [[ReallyBogus]]
>             Submitter = 345678
>             Carrier = NHIC
>             CvtCarrier = False
>             KeepLicense = False
>             KeepInsID = False
>             KeepTaxID = True
>             KeepUxIN = True
>             KeepFacID = False
>             UseSecID = False
>             FixSSN = True
>             DNtoDQ = False
>             InFile = E:\ultrahld\MCARE03.837
>             OutFile = E:\bbs\out.837
>
>
> If I cut the file short after [JobProfiles], all is well, but if I 
> include [[Bogus]] or [[ReallyBogus]] the validation blows up with the 
> following:
> Traceback (most recent call last):
>
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 538, in <module>
>     main()
>      File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 530, in main
>     test = Global.cfgFile.validate(Global.vtor, copy=True)
>      File "c:\python25\lib\site-packages\configobj.py", line 2301, in
>     validate
>     copy=copy, section=section[entry])
>      File "c:\python25\lib\site-packages\configobj.py", line 2297, in
>     validate
>     section.comments[entry] = section._cs_section_comments[entry]
>     KeyError: 'Bogus'
>     Script terminated.
>
>
> I was poking around adding pprint() statements in configobj.py, and 
> the problem seems to be that when "__many__" occurs in the configspec, 
> no entries are created in section._cs_section_comments - which of 
> course they wouldn't be, because we don't know what the subsection 
> names are yet.
>
> I'm not actually using comments, and probably never will, so I suppose 
> I could just rip out all of that... but there must be a better way, 
> and I can't possibly be the only one who's run into this.  However, I 
> haven't seen it mentioned in the list archives, so I suspect I'm doing 
> something wrong.  What should I do?
>
> Windows XP Pro SP3
> Python 2.5.1
> wxPython 2.8.7.1 <http://2.8.7.1>
> ConfigObj 4
>
> -- 
> www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   


-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/

Re: [Configobj-develop] Hello?

[Marc T. <mar...@gm...>]

On Sat, Jun 21, 2008 at 2:44 PM, Michael Foord <fuz...@vo...>
wrote:

> Hello Marc,
>
> I don't use the sourceforge support boards - this is the right place to
> ask questions, but I'm in the middle of writing a book (well, near the
> end actually) and so will have to find time to squeeze in looking at
> your problem.
>
> Michael
>

Thank you, and good luck on the book!  As I said, I didn't want to be
impatient - I just wanted to be sure that my message had got through.  (Like
when you ring a doorbell outside a thick door.  You stand there wondering
"did it even ring the first time?  Should I push it again, or will I come
off as a jerk if I do?")

>     On Sat, Jun 21, 2008 at 11:43 AM, Michael Foord
> >     <fuz...@vo... <mailto:fuz...@vo...>>
> wrote:
> >
> >         Hello. :-)
> >
> >         I sent a reply a couple of hours ago. Did you get it?
> >
> >         Michael
>

I still haven't seen that.  If it was a reply to my question, could you
re-send it, please?  If it was just "OK, I heard you", then no problem.

Again, thank you for the excellent module, and good luck on the book!

-- 
www.fsrtechnologies.com

Re: [Configobj-develop] Hello?

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

Marc Tompkins wrote:
> Looking at the support-requests board on SourceForge, it appears I 
> posted twice.  Please disregard the second one!

Hello Marc,

I don't use the sourceforge support boards - this is the right place to 
ask questions, but I'm in the middle of writing a book (well, near the 
end actually) and so will have to find time to squeeze in looking at 
your problem.

Michael

> On Sat, Jun 21, 2008 at 1:18 PM, Marc Tompkins 
> <mar...@gm... <mailto:mar...@gm...>> wrote:
>
>     I got this one, but not the other.  It's not in my Spam folder
>     either.
>
>
>     On Sat, Jun 21, 2008 at 11:43 AM, Michael Foord
>     <fuz...@vo... <mailto:fuz...@vo...>> wrote:
>
>         Hello. :-)
>
>         I sent a reply a couple of hours ago. Did you get it?
>
>         Michael
>
>
>         Marc Tompkins wrote:
>         > I submitted a question a few days ago, and haven't heard any
>         > response.  I don't want to seem impatient - that's not it -
>         but I just
>         > looked at the list archive, and my question never appeared
>         there.  So
>         > this is a test.  Can anybody hear me?
>         >
>         > --
>         > www.fsrtechnologies.com <http://www.fsrtechnologies.com>
>         <http://www.fsrtechnologies.com>
>         >
>         ------------------------------------------------------------------------
>         >
>         >
>         -------------------------------------------------------------------------
>         > Check out the new SourceForge.net Marketplace.
>         > It's the best place to buy or sell services for
>         > just about anything Open Source.
>         > http://sourceforge.net/services/buy/index.php
>         >
>         ------------------------------------------------------------------------
>         >
>         > _______________________________________________
>         > Configobj-develop mailing list
>         > Con...@li...
>         <mailto:Con...@li...>
>         > https://lists.sourceforge.net/lists/listinfo/configobj-develop
>         >
>
>
>         --
>         http://www.ironpythoninaction.com/
>         http://www.theotherdelia.co.uk/
>         http://www.voidspace.org.uk/
>         http://www.ironpython.info/
>         http://www.resolverhacks.net/
>
>
>         -------------------------------------------------------------------------
>         Check out the new SourceForge.net Marketplace.
>         It's the best place to buy or sell services for
>         just about anything Open Source.
>         http://sourceforge.net/services/buy/index.php
>         _______________________________________________
>         Configobj-develop mailing list
>         Con...@li...
>         <mailto:Con...@li...>
>         https://lists.sourceforge.net/lists/listinfo/configobj-develop
>
>
>
>
>     -- 
>     www.fsrtechnologies.com <http://www.fsrtechnologies.com> 
>
>
>
>
> -- 
> www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   


-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/

Re: [Configobj-develop] Hello?

[Marc T. <mar...@gm...>]

On Sat, Jun 21, 2008 at 1:19 PM, Marc Tompkins <mar...@gm...>
wrote:

> Looking at the support-requests board on SourceForge, it appears I posted
> twice.  Please disregard the second one!


Just deleted it.  Disregard!

-- 
www.fsrtechnologies.com

Re: [Configobj-develop] Hello?

[Marc T. <mar...@gm...>]

Looking at the support-requests board on SourceForge, it appears I posted
twice.  Please disregard the second one!

On Sat, Jun 21, 2008 at 1:18 PM, Marc Tompkins <mar...@gm...>
wrote:

> I got this one, but not the other.  It's not in my Spam folder either.
>
>
> On Sat, Jun 21, 2008 at 11:43 AM, Michael Foord <fuz...@vo...>
> wrote:
>
>> Hello. :-)
>>
>> I sent a reply a couple of hours ago. Did you get it?
>>
>> Michael
>>
>>
>> Marc Tompkins wrote:
>> > I submitted a question a few days ago, and haven't heard any
>> > response.  I don't want to seem impatient - that's not it - but I just
>> > looked at the list archive, and my question never appeared there.  So
>> > this is a test.  Can anybody hear me?
>> >
>> > --
>> > www.fsrtechnologies.com <http://www.fsrtechnologies.com>
>> > ------------------------------------------------------------------------
>> >
>> >
>> -------------------------------------------------------------------------
>> > Check out the new SourceForge.net Marketplace.
>> > It's the best place to buy or sell services for
>> > just about anything Open Source.
>> > http://sourceforge.net/services/buy/index.php
>> > ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Configobj-develop mailing list
>> > Con...@li...
>> > https://lists.sourceforge.net/lists/listinfo/configobj-develop
>> >
>>
>>
>> --
>> http://www.ironpythoninaction.com/
>> http://www.theotherdelia.co.uk/
>> http://www.voidspace.org.uk/
>> http://www.ironpython.info/
>> http://www.resolverhacks.net/
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Configobj-develop mailing list
>> Con...@li...
>> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>>
>
>
>
> --
> www.fsrtechnologies.com




-- 
www.fsrtechnologies.com

Re: [Configobj-develop] Hello?

[Marc T. <mar...@gm...>]

I got this one, but not the other.  It's not in my Spam folder either.

On Sat, Jun 21, 2008 at 11:43 AM, Michael Foord <fuz...@vo...>
wrote:

> Hello. :-)
>
> I sent a reply a couple of hours ago. Did you get it?
>
> Michael
>
>
> Marc Tompkins wrote:
> > I submitted a question a few days ago, and haven't heard any
> > response.  I don't want to seem impatient - that's not it - but I just
> > looked at the list archive, and my question never appeared there.  So
> > this is a test.  Can anybody hear me?
> >
> > --
> > www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Configobj-develop mailing list
> > Con...@li...
> > https://lists.sourceforge.net/lists/listinfo/configobj-develop
> >
>
>
> --
> http://www.ironpythoninaction.com/
> http://www.theotherdelia.co.uk/
> http://www.voidspace.org.uk/
> http://www.ironpython.info/
> http://www.resolverhacks.net/
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>



-- 
www.fsrtechnologies.com

Re: [Configobj-develop] Hello?

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

Hello. :-)

I sent a reply a couple of hours ago. Did you get it?

Michael


Marc Tompkins wrote:
> I submitted a question a few days ago, and haven't heard any 
> response.  I don't want to seem impatient - that's not it - but I just 
> looked at the list archive, and my question never appeared there.  So 
> this is a test.  Can anybody hear me?
>
> -- 
> www.fsrtechnologies.com <http://www.fsrtechnologies.com>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>   


-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/

[Configobj-develop] Hello?

[Marc T. <mar...@gm...>]

I submitted a question a few days ago, and haven't heard any response.  I
don't want to seem impatient - that's not it - but I just looked at the list
archive, and my question never appeared there.  So this is a test.  Can
anybody hear me?

-- 
www.fsrtechnologies.com

Re: [Configobj-develop] Validating with __many__...

[Marc T. <mar...@gm...>]

On Thu, Jun 19, 2008 at 6:25 PM, Marc Tompkins <mar...@gm...>
wrote:

>
> ConfigObj 4
>

Sorry, forgot to fill in the rest before hitting send...

ConfigObj 4.5.2
-- 
www.fsrtechnologies.com

[Configobj-develop] Validating with __many__...

[Marc T. <mar...@gm...>]

Hi all -

I hope this is not a horribly stupid question...

I'm setting up my configspec thusly:


>     tmpStr = """[Current]
>     npiXMLFile = string(default="npiMap.XML")
>     InHist = string_list(default=None)
>     OutHist = string_list(default=None)
>     Submitter = string(default=None)
>     Carrier = string(default=None)
>     MainSize = tuple()
>     MainPos = tuple()
>     SummarySize = tuple()
>     SummaryPos = tuple()
>     ConfirmSuccess = boolean(default=True)
>     CvtCarrier = boolean(default=False)
>     KeepLicense = boolean(default=False)
>     KeepInsID = boolean(default=False)
>     KeepTaxID = boolean(default=True)
>     KeepUxIN = boolean(default=True)
>     KeepFacID = boolean(default=False)
>     UseSecID = boolean(default=False)
>     FixSSN = boolean(default=True)
>     DNtoDQ = boolean(default=False)
>     [JobProfiles]
>     [[__many__]]
>     Submitter = string(default=" ")
>     Carrier = string(default=" ")
>     CvtCarrier = boolean(default=False)
>     KeepLicense = boolean(default=False)
>     KeepInsID = boolean(default=False)
>     KeepTaxID = boolean(default=True)
>     KeepUxIN = boolean(default=True)
>     KeepFacID = boolean(default=False)
>     UseSecID = boolean(default=False)
>     FixSSN = boolean(default=True)
>     DNtoDQ = boolean(default=False)
>     InFile = string(default="")
>     OutFile = string(default="")
>     """
>     cfgSpec = StringIO.StringIO(tmpStr)
>     cfgFile = ConfigObj(cfgFileName,
>                 configspec=cfgSpec, raise_errors=True, write_empty_values =
> True,
>                 create_empty=True, indent_type='    ', list_values = True)
>     vtor = Validator()
>

and validating it thusly:

>     test = cfgFile.validate(vtor, copy=True)
>     cfgFile.write()
>

My actual ini file looks like so:

> [Current]
>     npiXMLFile = file:///E:/ultrahld/npiMap.xml
>     Submitter = 1234567
>     Carrier = ColoradoMedicare
>     ConfirmSuccess = True
>     KeepLicense = False
>     KeepInsID = False
>     KeepTaxID = True
>     KeepUxIN = False
>     KeepFacID = False
>     UseSecID = True
>     FixSSN = True
>     DNtoDQ = False
>     InHist = E:\ultrahld\MCARE06.837, E:\ultrahld\MCARE04.837,
> E:\bbs\out.837
>     OutHist = E:\bbs\out.837, E:\bbs\MCAL03.NPI
>     CvtCarrier = True
> [JobProfiles]
>     [[Bogus]]
>         Submitter = 8675309
>         Carrier = NHIC
>         CvtCarrier = False
>         KeepLicense = False
>         KeepInsID = False
>         KeepTaxID = True
>         KeepUxIN = True
>         KeepFacID = False
>         UseSecID = False
>         FixSSN = True
>         DNtoDQ = False
>         InFile = E:\ultrahld\MCARE04.837
>         OutFile = E:\bbs\out.837
>     [[ReallyBogus]]
>         Submitter = 345678
>         Carrier = NHIC
>         CvtCarrier = False
>         KeepLicense = False
>         KeepInsID = False
>         KeepTaxID = True
>         KeepUxIN = True
>         KeepFacID = False
>         UseSecID = False
>         FixSSN = True
>         DNtoDQ = False
>         InFile = E:\ultrahld\MCARE03.837
>         OutFile = E:\bbs\out.837
>

If I cut the file short after [JobProfiles], all is well, but if I include
[[Bogus]] or [[ReallyBogus]] the validation blows up with the following:
Traceback (most recent call last):

>  File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 538, in <module>
> main()
>  File "E:\fsrPy\FSR-X12\fsr_x12.pyw", line 530, in main
> test = Global.cfgFile.validate(Global.vtor, copy=True)
>  File "c:\python25\lib\site-packages\configobj.py", line 2301, in validate
> copy=copy, section=section[entry])
>  File "c:\python25\lib\site-packages\configobj.py", line 2297, in validate
> section.comments[entry] = section._cs_section_comments[entry]
> KeyError: 'Bogus'
> Script terminated.
>

I was poking around adding pprint() statements in configobj.py, and the
problem seems to be that when "__many__" occurs in the configspec, no
entries are created in section._cs_section_comments - which of course they
wouldn't be, because we don't know what the subsection names are yet.

I'm not actually using comments, and probably never will, so I suppose I
could just rip out all of that... but there must be a better way, and I
can't possibly be the only one who's run into this.  However, I haven't seen
it mentioned in the list archives, so I suspect I'm doing something wrong.
What should I do?

Windows XP Pro SP3
Python 2.5.1
wxPython 2.8.7.1
ConfigObj 4

-- 
www.fsrtechnologies.com

Re: [Configobj-develop] including files in files

[Dan G. <dkg...@lb...>]

Michael Foord wrote:
> Hello Dan,
>
> The section method 'merge' can be used to merge config files that are 
> read in separately. At least if you read them in individually the error 
> messages will be correct.
>
>   
Aha! Thanks for the suggestion. One trick though is that in order to 
handle the case where A includes B and C, and C uses some values from B, 
I had to go ahead and merge the include files with each other as well. 
Anyways, my new-and-improved version, complete with proper error 
reporting, is below. Any further suggestions for improvement would of 
course be appreciated. Hopefully someone else gets some mileage out of 
this too..

Thanks,

-Dan
> Michael Foord
> http://www.ironpythoninaction.com/
>   
import configobj
class IncConfigObj(configobj.ConfigObj):
    """Recognize and process '#@include <file>' directives
    transparently. Do not deal with recursive references, i.e.
    ignore directives inside included files.
    """
    def __init__(self, infile, **kw):
        """Take same arguments as ConfigObj, but in the case of a file
        object or filename, process #@include statements in the file.
        """  
        configobj.ConfigObj.__init__(self, infile, **kw)
        if isinstance(infile,str) or hasattr(infile,'read'):
            if hasattr(infile, 'read'):
                f = infile
                f.seek(0) # rewind to start of file
            else:
                f = file(infile)
            # walk through input file
            included = { } # combination of all included files
            for line in f:
                # look for include directive
                s = line.strip()
                if s.startswith('#') and \
                        s[1:].strip().startswith('@include'):
                    # open and read the include file
                    inc_path = s[1:].strip().split(None,1)[1]
                    try:
                        inc = configobj.ConfigObj(inc_path, **kw)
                    except configobj.ConfigObjError, E:
                        raise configobj.ConfigObjError(
                        "in included file '%s': %s" % (inc_path, E))
                    # merge in previous included file(s)
                    inc.merge(included)
                    included = inc
            # merge included files into the top-level
            self.merge(included)

-- 
Dan Gunter. voice:510-495-2504 fax:510-486-6363 dsd.lbl.gov/~dang

Re: [Configobj-develop] including files in files

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

Hello Dan,

The section method 'merge' can be used to merge config files that are 
read in separately. At least if you read them in individually the error 
messages will be correct.

Michael Foord
http://www.ironpythoninaction.com/

Dan Gunter wrote:
> Hi,
>
> I have a situation where there is some shared information across a 
> couple of configuration files and I'd like to include one config file in 
> another (one level of include is fine). I would welcome clever and/or 
> built-in solutions to this problem. But I thought I would share; below 
> is my ConfigObj subclass that I use (as a drop-in replacement to 
> ConfigObj) to solve it. Note that one thing missing from this solution 
> is proper re-mapping of files and line numbers in error messages.
>
> -Dan
>
> class IncConfigObj(configobj.ConfigObj):
>     """Recognize and process '@include <file>' directives
>     transparently. Do not deal with recursive references, i.e.
>     ignore @includes inside included files.
>     """
>     def __init__(self, infile, **kw):
>         """Take same arguments as ConfigObj, but in the case of a file
>         object or filename, process @include statements in the file.
>         """
>
>         if not isinstance(infile, str) and not hasattr(infile, 'read'):
>             arg = infile # pass to ConfigObj unmodified
>         # yes, it's a file-like-object or string (filename)
>         else:
>             arg = [ ]
>             if isinstance(infile, file):
>                 f = infile
>             else:
>                 f = file(infile)
>             # walk through input file
>             for line in f:
>                 # look for include directive
>                 if line.strip().startswith('@include'):
>                     # open the include file
>                     inc_path = line.strip().split(None,1)[1]
>                     try:
>                         f = file(inc_path)
>                     except IOError,E:
>                         raise IOError("opening included file "
>                                       "'%s': %s" % (inc_path, E))
>                     # include the given file
>                     for inc_line in f:
>                         arg.append(inc_line)
>                 # otherwise just keep going
>                 else:
>                     arg.append(line)
>         configobj.ConfigObj.__init__(self, arg, **kw)
>
>   

[Configobj-develop] including files in files

[Dan G. <dkg...@lb...>]

Hi,

I have a situation where there is some shared information across a 
couple of configuration files and I'd like to include one config file in 
another (one level of include is fine). I would welcome clever and/or 
built-in solutions to this problem. But I thought I would share; below 
is my ConfigObj subclass that I use (as a drop-in replacement to 
ConfigObj) to solve it. Note that one thing missing from this solution 
is proper re-mapping of files and line numbers in error messages.

-Dan

class IncConfigObj(configobj.ConfigObj):
    """Recognize and process '@include <file>' directives
    transparently. Do not deal with recursive references, i.e.
    ignore @includes inside included files.
    """
    def __init__(self, infile, **kw):
        """Take same arguments as ConfigObj, but in the case of a file
        object or filename, process @include statements in the file.
        """

        if not isinstance(infile, str) and not hasattr(infile, 'read'):
            arg = infile # pass to ConfigObj unmodified
        # yes, it's a file-like-object or string (filename)
        else:
            arg = [ ]
            if isinstance(infile, file):
                f = infile
            else:
                f = file(infile)
            # walk through input file
            for line in f:
                # look for include directive
                if line.strip().startswith('@include'):
                    # open the include file
                    inc_path = line.strip().split(None,1)[1]
                    try:
                        f = file(inc_path)
                    except IOError,E:
                        raise IOError("opening included file "
                                      "'%s': %s" % (inc_path, E))
                    # include the given file
                    for inc_line in f:
                        arg.append(inc_line)
                # otherwise just keep going
                else:
                    arg.append(line)
        configobj.ConfigObj.__init__(self, arg, **kw)

-- 
Dan Gunter. voice:510-495-2504 fax:510-486-6363 dsd.lbl.gov/~dang

Re: [Configobj-develop] ConfigObj type validation/coercion issue

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

Hello Jesse,

Sorry for the late reply. Looking at it, it seems to be quite a serious 
problem and I can't see anything you have done wrong.

I'll try and look at this in more detail tonight - I've cc'ed the 
configobj-develop mailing list.


Michael
http://www.ironpythoninaction.com

Jesse Noller wrote:
> He Michael - I hope you don't mind me dropping you a line about this -
>
> Using the latest configObj and validator code - I am trying to build
> up a config file and spec and then do the validation/type coercion on
> it offered by configObj - and I am running into a mystifying issue -
> for example, here is the config file:
>
> ["network_options"]
> portal_port =
>
> And here is the spec:
> ["network_options"]
> portal_port = integer(min=0, default=8082)
>
> When I try this:
>
>     vdt = Validator()
>     configspec = ConfigObj('config.spec')
>     config = ConfigObj(configFile, configspec=configspec)
>     config.validate(vdt)
>
> It explodes with:
>
> Traceback (most recent call last):
>   File "ctransfer.py", line 92, in <module>
>     sys.exit(main(sys.argv[1]))
>   File "ctransfer.py", line 85, in main
>     config = load_conf


> ig(configFile)
>   File "ctransfer.py", line 49, in load_config
>     config.validate(vdt)
>   File "/Library/Python/2.5/site-packages/configobj.py", line 2301, in validate
>     copy=copy, section=section[entry])
>   File "/Library/Python/2.5/site-packages/configobj.py", line 2245, in validate
>     missing=missing
>   File "/Library/Python/2.5/site-packages/validate.py", line 595, in check
>     fun_name, fun_args, fun_kwargs, default = self._parse_with_caching(check)
>   File "/Library/Python/2.5/site-packages/validate.py", line 620, in
> _parse_with_caching
>     if check in self._cache:
> TypeError: list objects are unhashable
>
> I added some debugging (print statements for the win) to the code and
> found that check looks like this:
>
> ['integer(min=0', 'default=8082)']
>
> So on line 619 - check is actually being passed in as a list so the if
> check in self._cache check fails. Did I do something horribly wrong
> here?
>
> -jesse
>   

Re: [Configobj-develop] Logging and ConfigObj

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

Dan Gunter wrote:
> being new to the list, I was looking at the archives and came across 
> this post on Nov. 2007.
>
> If this is still an open question, an easy answer is: look at how 
> TurboGears uses configobj to do exactly this!
>   

I don't remember this email - thanks for the info!

Michael Foord
http://www.ironpythoninaction.com/

>> When I needed a way to specify configuration parameters for my program, I
>> chose ConfigObj without looking closely at ConfigParser very closely 
>> because
>> I had a feeling ConfigObj was better. Recently, I started using the 
>> logging
>> package with my software. It allows me to specify its configuration 
>> using a
>> configuration file, but it uses ConfigParser to access it. I would 
>> like to
>> keep all configuration data in one configuration file, so I figured 
>> that it
>> wouldn't be a big deal to switch my software over to ConfigParser. When I
>> first encountered get/set, my stomach twisted. When I discovered that I
>> couldn't specify a list as an option, I aborted. I was transforming code
>> that was simple and transparent into something verbose and opaque. 
>> Because
>> my configuration file is not compatible with ConfigParser, I am 
>> resigned to
>> two configuration files, one for my code and one for logging. However, 
>> I am
>> wondering first whether I am missing a one-configuration-file solution. I
>> suppose that logging needs to be updated to use ConfigObj, but perhaps 
>> I am
>> missing a solution that I can apply more readily.
>> -- 
>> Jeffrey Barish 
>>     
> -Dan
>
>   

[Configobj-develop] Logging and ConfigObj

[Dan G. <dkg...@lb...>]

being new to the list, I was looking at the archives and came across 
this post on Nov. 2007.

If this is still an open question, an easy answer is: look at how 
TurboGears uses configobj to do exactly this!
> When I needed a way to specify configuration parameters for my program, I
> chose ConfigObj without looking closely at ConfigParser very closely 
> because
> I had a feeling ConfigObj was better. Recently, I started using the 
> logging
> package with my software. It allows me to specify its configuration 
> using a
> configuration file, but it uses ConfigParser to access it. I would 
> like to
> keep all configuration data in one configuration file, so I figured 
> that it
> wouldn't be a big deal to switch my software over to ConfigParser. When I
> first encountered get/set, my stomach twisted. When I discovered that I
> couldn't specify a list as an option, I aborted. I was transforming code
> that was simple and transparent into something verbose and opaque. 
> Because
> my configuration file is not compatible with ConfigParser, I am 
> resigned to
> two configuration files, one for my code and one for logging. However, 
> I am
> wondering first whether I am missing a one-configuration-file solution. I
> suppose that logging needs to be updated to use ConfigObj, but perhaps 
> I am
> missing a solution that I can apply more readily.
> -- 
> Jeffrey Barish 
-Dan

-- 
Dan Gunter. voice:510-495-2504 fax:510-486-6363 dsd.lbl.gov/~dang

Re: [Configobj-develop] Minor bug: validate.py needs higer Python version

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

Hi Robert,

*Damn*. That could be a straight list comprehension and it should work 
fine on Python 2.3. I'll fix that in a future release...

Michael

Robert Nikutta wrote:
> Hi Michael,
>
> today it's about validate.py. I'm using the wonderful combination of
> configobj.py and validate.py (v0.3.1), which work great, thanks a lot
> for this.
>
> Today I tried to run this on an other machine that has Python 2.3.4
> installed (CentOS). This failed, complaining about syntax error in
> validate.py. Here's the traceback:
>
> -----
> Traceback (most recent call last):
>   File "./clumpy.py", line 1196, in ?
>     import configobj, validate
>   File "src/python/validate.py", line 627
>     fun_kwargs = dict((str(key), value) for (key, value) in
> fun_kwargs.items())
>                                           ^
> SyntaxError: invalid syntax
> -----
>
> I see that the code states that Python >= 2.2 should be fine, but it
> obviously isn't.
>
> I installed Python 2.5.2, and it runs again, of course.
>
> Best,
> Robert
>
>   

Re: [Configobj-develop] [PATCH] Don't use hasattr

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

Matt Nordhoff wrote:
> Michael Foord wrote:
>   
>> Matt Nordhoff wrote:
>>     
>>> Hi.
>>>
>>> Python's hasattr() function swallows all exceptions, including things
>>> like KeyboardInterrupt. Therefore, one project I tinker on (Bazaar) uses
>>> "getattr(object, 'attribute', None) is not None" instead. Here's a patch
>>> to change that in ConfigObj (and pathutils).
>>>
>>> Of course, that is subtly different, so you should verify it's ok. I
>>> didn't run ConfigObj's test suite (unless it has no output and takes 1
>>> second, in which case I did), but I did run Bazaar's test suite with
>>> this change and nothing broke.
>>>   
>>>       
>> Is the current use of hasattr *actually* causing any problems - or is it 
>> to avoid potential problems?
>>     
>
> To avoid potential problems.
>
>   
>> I can see any problem with the patch though... (not likely to be a new 
>> release *soon* but can apply to SVN).
>>     
>
> "can" or "can't"?
>
>   

Well the patch looks harmless enough and not likely to confuse - so I 
meant 'can'. I doubt the problem it solves is ever likely to be a real 
problem though... :-)

Michael

>> Michael Foord
>> http://www.manning.com/foord
>>     
>
> Hmm, I didn't mean this message to be so terse..
>   

Re: [Configobj-develop] [PATCH] Don't use hasattr

[Matt N. <mno...@ma...>]

Michael Foord wrote:
> Matt Nordhoff wrote:
>> Hi.
>>
>> Python's hasattr() function swallows all exceptions, including things
>> like KeyboardInterrupt. Therefore, one project I tinker on (Bazaar) uses
>> "getattr(object, 'attribute', None) is not None" instead. Here's a patch
>> to change that in ConfigObj (and pathutils).
>>
>> Of course, that is subtly different, so you should verify it's ok. I
>> didn't run ConfigObj's test suite (unless it has no output and takes 1
>> second, in which case I did), but I did run Bazaar's test suite with
>> this change and nothing broke.
>>   
> 
> Is the current use of hasattr *actually* causing any problems - or is it 
> to avoid potential problems?

To avoid potential problems.

> I can see any problem with the patch though... (not likely to be a new 
> release *soon* but can apply to SVN).

"can" or "can't"?

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

Hmm, I didn't mean this message to be so terse..
-- 

Re: [Configobj-develop] [PATCH] Don't use hasattr

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

Matt Nordhoff wrote:
> Hi.
>
> Python's hasattr() function swallows all exceptions, including things
> like KeyboardInterrupt. Therefore, one project I tinker on (Bazaar) uses
> "getattr(object, 'attribute', None) is not None" instead. Here's a patch
> to change that in ConfigObj (and pathutils).
>
> Of course, that is subtly different, so you should verify it's ok. I
> didn't run ConfigObj's test suite (unless it has no output and takes 1
> second, in which case I did), but I did run Bazaar's test suite with
> this change and nothing broke.
>   

Is the current use of hasattr *actually* causing any problems - or is it 
to avoid potential problems?

I can see any problem with the patch though... (not likely to be a new 
release *soon* but can apply to SVN).

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

> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> 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] [PATCH] Don't use hasattr

[Matt N. <mno...@ma...>]

Hi.

Python's hasattr() function swallows all exceptions, including things
like KeyboardInterrupt. Therefore, one project I tinker on (Bazaar) uses
"getattr(object, 'attribute', None) is not None" instead. Here's a patch
to change that in ConfigObj (and pathutils).

Of course, that is subtly different, so you should verify it's ok. I
didn't run ConfigObj's test suite (unless it has no output and takes 1
second, in which case I did), but I did run Bazaar's test suite with
this change and nothing broke.
-- 

Re: [Configobj-develop] ConfigObj 4.5.2 and validate 0.3.2

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

[ Michael Foord <mi...@vo...> ]
> I've just done a new release of validate and ConfigObj. This is validate
> 0.3.2 and ConfigObj 4.5.2 and fixes the bug where default values of None
> in configspecs were broken.
>
> http://www.voidspace.org.uk/python/configobj.html
> http://www.voidspace.org.uk/python/validate.html

Much thanks!!


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

[Configobj-develop] ConfigObj 4.5.2 and validate 0.3.2

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

Hello all,

I've just done a new release of validate and ConfigObj. This is validate 
0.3.2 and ConfigObj 4.5.2 and fixes the bug where default values of None 
in configspecs were broken.

http://www.voidspace.org.uk/python/configobj.html
http://www.voidspace.org.uk/python/validate.html

I've just switched to a Mac desktop and I've had to update my 
build/release process - so it has taken longer than usual and I haven't 
yet built new eggs or updated PyPI.

All the best,

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