Re: [Configobj-develop] Why does my config file behave this way?

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

On 10/02/2010 16:15, Jason Baker wrote:
> Here's a simplified version of a config file I'm using for envbuilder:
>
>     [[sbcl]]
>     setup = 'cp $CWD/customize-target-features.lisp $dir', 'sh 
> make.sh', 'sh install.sh'
>
> $CWD is an option that I implicitly define at the toplevel to be the 
> directory from which envb is run, and $dir has a default.  Each item 
> in this list is a terminal command that's supposed to be part of a 
> build process.
>
> I'm getting some weird behavior that I suspect has to do with me using 
> validation and interpolation.  As it stands right now, setup isn't 
> defined in the configspec.  And so when I do the above, none of the 
> values get interpolated.  IE, the first command that gets issued is 
> literally "cp $CWD/customize-target-features.lisp $dir".  However, if 
> I changed it to be a single string, it works fine.  I can make this 
> work properly if I add a setup option in the configspec and set it to 
> force_list.  Thus, this is working for me.  I just want to get a 
> better understanding of what's going on here.  Can anyone shed some 
> light on it?

What version of ConfigObj are you using? I'm pretty sure that 
interpolation in list values was only just added in the 4.7 release.

Michael

>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
>
>
> _______________________________________________
> Configobj-develop mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/configobj-develop
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.