On Mon, Apr 19, 2010 at 10:28:37AM -0400, Jim Fulton wrote:
On Mon, Apr 19, 2010 at 10:00 AM, Florian Friesdorf <flo@chaoflow.net> wrote:
Hi Jim, hi Christian,
any further thoughts on this?
Not at this time. This is on my to-do list to look at.
I think your use case would be better handled through normal command-line option specification, as in:
buildout -c deploy.cfg buildout:extends+=site1.cfg
but that doesn't work. I think that should work and want to look at why it doesn't.
That'd be nice and would be sufficient for my current use case. And the discussion about environment variables we could continue on the base of this being functional. I took a look at it and so far came up with two docstrings (attached). I think I could simplify _open and make extends work as expected, in case you are comfortable with delegating that (see also 'desired behaviour' in the docstring for _open (attached). florian -- Florian Friesdorf <flo@chaoflow.net> GPG FPR: EA5C F2B4 FBBB BA65 3DCD E8ED 82A1 6522 4A1F 4367 Jabber/XMPP: flo@chaoflow.net OTR FPR: 9E191746 213321FE C896B37D 24B118C0 31785700 IRC: chaoflow on freenode,ircnet,blafasel,OFTC