Please add a way to optionally extend

[James Westby]

Hi,

I use a version control system. I want to version control my buildout configuration.

I also want people to be able to get started by just running buildout.

However, I also sometimes want to make local tweaks to my buildout configuration,
such as an extra develop directory, or offline mode. I also want to recommend
this to contributors from time to time.

Unfortunately this means that they will sometimes mistakenly commit changes
to the buildout configuration with local paths in it or similar.

Therefore it would be great if there was a way to "extends" but not require the
file to be present.

Then I could "extends-optional = local.cfg" and ignore the "local.cfg" in my VCS.

Instructions to contributors could then be to add things to local.cfg for local overrides,
which won't get committed, but there is no extra step required to get working.

Thanks,

James

[Martijn Pieters (mjpieters)]

Do this the other way around. Advise people to create a local.cfg that extends your buildout:

local.cfg:
[buildout]
extends = buildout.cfg

and put the overrides they need in there. Then ignore local.cfg in your VCS.