[Distutils] [buildout] extending a .cfg supplied by another package

[Wolfgang Schnerring]

* Tres Seaver <tseaver at palladion.com> [2010-05-14 16:10]:
> Wolfgang Schnerring wrote:
>> * Jim Fulton <jim at zope.com> [2010-05-12 21:51]:
>>> - A syntax proposal.  It has to address distinguishing file paths from
>>>   urls from these new things. I suspect these should be expressed as
>>>   URLs, e.g.:
>>>      project://some.project/aconfig.cfg
>> 
>> I'd propose egg://some.dotted.name/config.cfg
>
> I think egg:some.dotted.name#config.cfg would be clearer:  the
> "hierarchical" URL form is misleading.

Agreed, that makes sense to me.

> We could even adopt the convention that such config files needed to be
> registered as entry points under some given section, e.g.:

Using entry points sounds good. One could even define a default one
(named... "default", maybe? ;), so you could just reference
egg://some.dotted.name without a #filename.cfg modifier.

Wolfgang