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 create a
>> zope.hookable with a Python + C implementation.
> Even if it does bring significant speedups, why does it need to be a
> seperate package?
It doesn't, but it's already a package that could be easily turned into
something with proper documentation (it's mostly there, just hidden),
and one of the goals was to reduce C dependencies in zope.component, not
add C code to it.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -