Sure the actual startup of the extension must depend on cfg key. I'm thinking of generic / cross-framework components that would be installed on the platform say for another framework but you don't want enabled in your project; or even with upcoming multiapp support in CP 2.2 one feature you want in app1 but not in app2.
Bob: Yes I'll vote for more Paste support (but I think that's already clear from my previous mails in TG ML but the CP and Paste ones too) Jeff: did you peek at Paste.auth ? Bob Ippolito wrote: > > > On Jan 10, 2006, at 4:16 PM, Jeff Watkins wrote: > >> I'd like to propose a new entrypoint for TurboGears: >> turbogears.extension. The entrypoint will be a function to call on >> startup that can register a filter or whatever. >> >> The first extensions would be the Visit Tracking and Identity >> framework. This way, if you don't want Identity and Visit Tracking, >> you don't easy_install them. >> >> Thoughts? > > I think it's a bad idea to activate some feature just because it > happens to be installed. You should have to explicitly ask for those > features to be activated somehow. Perhaps list the entry points in > the dev.cfg/prod.cfg. PasteDeploy <http://pythonpaste.org/deploy/> > does something similar with its config files. > > -bob > >
signature.asc
Description: OpenPGP digital signature
