Re: [Zope-dev] implementing zope.component 4.0

2009-11-27 Thread Chris Withers
Marius Gedminas wrote: What's the motivation? The utilities must be singletons logic hardcoded in the ZCA. provideAdapter(factory, adapts=(one, two, three)) provideAdapter(factory, adapts=(one, two)) provideAdapter(factory, adapts=(one, )) The natural progression, to me, is

Re: [Zope-dev] implementing zope.component 4.0

2009-11-27 Thread Martijn Faassen
Marius Gedminas wrote: [snip] The utilities must be singletons logic hardcoded in the ZCA. provideAdapter(factory, adapts=(one, two, three)) provideAdapter(factory, adapts=(one, two)) provideAdapter(factory, adapts=(one, )) The natural progression, to me, is provideAdapter(factory,

Re: [Zope-dev] implementing zope.component 4.0

2009-11-27 Thread Adam GROSZER
Hello Martijn, I had a feeling that adapter lookup can be alone slowish with lots of registrations. We had a large project that was cut in half and the z3c.form UI, which is rather heavily adaptation based got a boost after that. Friday, November 27, 2009, 4:25:44 PM, you wrote: MF Someone

Re: [Zope-dev] implementing zope.component 4.0

2009-11-27 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Are people okay with the proposed semantics? +1. Would people be okay with such an upgrade path? Any better ideas? I would start issuign DeprecationWarnings (yes, I know I'm their worst fan, but we can't keep BBB here, so

Re: [Zope-dev] implementing zope.component 4.0

2009-11-27 Thread Lennart Regebro
On Fri, Nov 27, 2009 at 13:11, Marius Gedminas mar...@gedmin.as wrote: Personally, I prefer Zope's syntax (decorators inside the class block) to Python's (decorators above the class block), aesthetically. Yes, but it doesn't work under Python 3. We don't need to remove the support for Python 2,

<    1   2