> I wonder if a more general solution wouldn't be to expand environment
> variables in buildout.cfg files. Then you'd be able to say
>
> [buildout]
> download-cache = $HOME/tmp/buildout-download-cache
>
> I think I'd like that better than ~ expansion, but honestly I don't
> have
> an immediate use case other than $HOME.
I'm not sure if I'd like it better or not. If we did something like
this though, I think I'd want to spell it a little differently.
I'm thinking that there might be some sort os pseudo section, say
ENVIRONMENT, so you could do:
${ENVIRONMENT:HOME}
You could even specify an ENVIRONMENT section in a buildout file to
provide a default. But the main reason I'd prefer something like this
is to not introduce a new variable-substitution syntax.
On Jan 8, 2009, at 4:10 PM, Barry Warsaw wrote:
> I wonder if a more general solution wouldn't be to expand environment buildout- download- cache
> variables in buildout.cfg files. Then you'd be able to say
>
> [buildout]
> download-cache = $HOME/tmp/
>
> I think I'd like that better than ~ expansion, but honestly I don't
> have
> an immediate use case other than $HOME.
I'm not sure if I'd like it better or not. If we did something like
this though, I think I'd want to spell it a little differently.
I'm thinking that there might be some sort os pseudo section, say
ENVIRONMENT, so you could do:
${ENVIRONME NT:HOME}
You could even specify an ENVIRONMENT section in a buildout file to substitution syntax.
provide a default. But the main reason I'd prefer something like this
is to not introduce a new variable-
Jim
--
Jim Fulton
Zope Corporation