On Mar 16, 2007, at 5:23 AM, Lennart Regebro wrote: > On 2/19/07, Christian Theune <[EMAIL PROTECTED]> wrote: >> [buildout] >> extends = profiles/dev.cfg >> >> and run bin/buildout. >> >> This works very well for us. > > It did for me too, but it has now stopped working.
I don't know what "it" is. I have no problem extending a configuration file in a subdirectory. In fact, i tried the example above (as much as is shown) without difficulty. > Line 89 in buildout.py says: > > data['buildout']['directory'] = os.path.dirname > (config_file) > > This must be a recent change (< 2 weeks) No. Buildout has always set the default buildout directory to the directory containing the configuration file given on the command line or to the current working directory. BTW, svn blame shows that that line was last modified on Dec 7. > because this makes buildout > fail if you have the cfg files anywhere else than root. I can't reproduce this. Can you construct a minimal example that illustrates this? Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
