17 May
2010
17 May
'10
3:58 a.m.
Tres Seaver wrote:
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.
How so? The .cfg could be a file in a folder in the egg, same as a template for bfg...
We could even adopt the convention that such config files needed to be registered as entry points under some given section, e.g.:
I don't see what purpose this would serve. I was ancticipating them being just like any other package_resource... Chris