On 2/23/07, Dieter Maurer <[EMAIL PROTECTED]> wrote:
Sidnei da Silva wrote at 2007-2-23 12:08 -0300:
> ...
>Wonder if we can just check for that? And then how to avoid a
>dependency of zope.interface on OFS.Uninstalled.BrokenClass.
You can positively check that the object is an "Interface" subcl
Sidnei da Silva wrote at 2007-2-23 12:08 -0300:
> ...
>Wonder if we can just check for that? And then how to avoid a
>dependency of zope.interface on OFS.Uninstalled.BrokenClass.
You can positively check that the object is an "Interface" subclass.
--
Dieter
FWIW, this is already a BrokenClass instance, thanks to ZODB:
(Pdb) p sequence
(Pdb) p sequence.__mro__
(, , , , , , , , , , , , , , , , , )
Wonder if we can just check for that? And then how to avoid a
dependency of zope.interface on OFS.Uninstalled.BrokenClass.
--
Sidnei da Silva
Enfold Syst
On 2/23/07, Jim Fulton <[EMAIL PROTECTED]> wrote:
I think this should be handled in the declaration serialization code.
We should arrange that when a declaration is unpickled we:
- catch interfaces that can't be loaded,
Apparently when the interface "can't be loaded" it turns from a
InterfaceC
On Feb 22, 2007, at 8:24 PM, Sidnei da Silva wrote:
Hi there,
I'm consistently having issues with 'directlyProvides' and interfaces
that are moved or removed. The symptom is that when the persisted
declaration is unghostified a TypeError happens.
This is specially bad since in this case the '
