On Fri, Aug 28, 2009 at 5:35 AM, Jonathan Ballet<[email protected]> wrote: ... > We often use the 'extends' feature of Buildout to create customized > version of configuration files per-developer or per-buildbot. > > One nice feature of Buildout was that I can easily extend another > configuration file and add part to those specified in this 'base' file. > Then, if I launched the Buildout, I got all the parts from the base file > plus the one I defined in *my* configuration file. I was very happy. > > > Unfortunately, it seems that the new release 1.4.0 of Buildbot has broke > this feature and the new behavior seems to be: install only parts which > are *strictly* defined in the configuration file used by the Buildout, > and not the 'inherited' ones anymore. > > > I wrote a quick doctest which illustrate this problem (merely adapted > from other doctests):
... > I'm not sure the behavior I expect was actually really documented (I > don't find it in the documentation) but this was nice! Sure it is: http://pypi.python.org/pypi/zc.buildout#adding-and-removing-options > Should I report a bug for this Yes. It looks like we're missing a test. > or was it a necessary change for the new > version of Buildout? No. Thanks for alll of the analysis to demonstrate the problem. Jim -- Jim Fulton _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
