Jim Fulton wrote:
On Wed, May 12, 2010 at 8:17 AM, Chris Withers <[email protected]> wrote:
Hi All,
I'd like to be able to do:
[buildout]
extends=some.package:aconfig.cfg
That's an interesting idea.
Yeah, I finally took a look at the package_resources part of setuptools ;-)
Low, in the short term. A good first step would be to work out a
somewhat detailed proposal including:
- Descriptions of specific situations where this would solve a
problem,
So, we have a bunch of packages that all depend on each other.
We group all the boilerplate into one package, including things like
base buildout .cfg files and the like.
We currently have to specify http urls to tags on our svn server to
extend these .cfg's, it would be better if we could just say "extend
this configuration from that package"
with specific examples of how the proposed meachanism would
be applied.
The tricky bit from my perspective is that some.package would need to be
obtained before any parts had been run, but I guess the same is true of
repice packages and buildout extension packages, so I'm guessing this
problem has been solved already?
- 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'll note that I suspect you can do this now using a buildout
extension that installs a new URL handler in urtllib2.
That's an interesting idea! I'll certainly have a look...
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
