Jim Fulton wrote:
You are referring to:
http://pypi.python.org/pypi/zc.buildout/1.0.6#adding-and-removing-options
Yup.
extension1.cfg and extension2.cfg are set up but no examples use them
as far as I can see.
The last example extends extensions2.cfg, which extends extensions1.cfg.
Oh, right, 4th time of reading I see that... :-S
The demo also uses extending of configurations as well as buildout
extensions before these have been introduced as concepts.
Yup. That's annoying. This section should be moved until after extending
has been described and should use an extension.
I'm guessing you mean "shouldn't use an extension"? Extensions look like
something I don't ever want to have to use ;-)
when extension1.cfg is used, but there's no explanation of how this
works. Are option values always split on spaces
Yes
Okay, I don't know if there's a "this is how sections, names and values"
work section but if there isn't, there should be, and if there is, I
missed it and I don't remember reading anything about how and where
values are split ;-) (ie: does a recipe get the values pre-split or does
it need to split itself and therefore is it just convention that
prevents a recipe from splitting on other characters too?)
Where is this documented?
That section tries to explain it. The parsing rule should have been
stated. The example should be made simpler. The extension business
complicates it excessively.
Yup. Maybe just a simple bit on "this is how sections, names and values
work" would do it?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
