By my analysis, releasing a version of zope.interface with the fallback proposed in the patch is not a reasonable thing to do:
- For "normal" uses of zope.interface, the proposed fallback behavior won't ever be triggered - For the nevow case: making __hash__ "work" (i.e., not raise AttributeError) before assigning the instance's '__name__' will still lead to a later failure, because the value stored in the dict will not be findable: objects used as keys in a dict *must* have a '__hash__' which always returns the same value for a given instance. -- You received this bug notification because you are a member of Divmod- dev, which is the registrant for nevow. https://bugs.launchpad.net/bugs/811792 Title: AttributeError: 'MetaTypedInterface' object has no attribute '__name__' Status in Divmod Nevow: Confirmed Status in Tahoe, the Lovely Accessible File System: New Status in zope.interface: Invalid Bug description: This is with Nevow 0.10.0 and zope.interface 3.6.4. David-Sarah Hopwood and Drew Perttula each independently reported this error. (I haven't seen it personally, I'm just reporting what they posted.) Drew included a patch to zope.interface work-around it: http://drewp.quickwitretort.com/2011/07/08/0 http://codepad.org/wd1UUnhh To manage notifications about this bug go to: https://bugs.launchpad.net/nevow/+bug/811792/+subscriptions -- Mailing list: https://launchpad.net/~divmod-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~divmod-dev More help : https://help.launchpad.net/ListHelp
