Re: [Zope-dev] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch:

2009-03-18 Thread Christian Theune
Hi, On Tue, 2009-03-10 at 04:18 +0300, Dan Korostelev wrote: 2009/3/5 Martijn Faassen faas...@startifact.com: Chris Withers wrote: Martijn Faassen wrote: I think we can only make the correct determination if we get an idea of the performance implications. If it turns out the C code

Re: [Zope-dev] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch:

2009-03-09 Thread Dan Korostelev
2009/3/5 Martijn Faassen faas...@startifact.com: Chris Withers wrote: Martijn Faassen wrote: I think we can only make the correct determination if we get an idea of the performance implications. If it turns out the C code brings significant speedups in real-world applications, we should

Re: [Zope-dev] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch:

2009-03-05 Thread Chris Withers
Martijn Faassen wrote: I think we can only make the correct determination if we get an idea of the performance implications. If it turns out the C code brings significant speedups in real-world applications, we should create a zope.hookable with a Python + C implementation. Even if it

Re: [Zope-dev] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch:

2009-03-04 Thread Martijn Faassen
Tres Seaver wrote: [snip] It probably could be (in fact, I prototyped it there first). However, it turns out that zope.hookable has effectively *no* clients beyond zope.component, which meant that I could lose the 'install_requires' dependency altogether by moving the pure-Python bits to