-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Aspeli wrote:
> Tres Seaver wrote:
> 
>> In either case, I think TypeError (or maybe LookupError) is the *right*
>> choice:  we don't want to "hide" zope.component's API functions and then
>> turn around and require folks to import zope.component just to catch its
>> local exception types.
> 
> Yeah, that's a compelling reason.

I have checked in a branch which makes failed adaptation (inside the
__call__ of an interface) raise a LookupError instead of a TypeError:
the branch also documents the semantics of __call__.  I would like to
merge this to the trunk a 3.6.0 version (bumped to indicate the
quasi-API change).


http://svn.zope.org/zope.interface/branches/tseaver-raise_lookup_error/?rev=106688&view=rev



Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tsea...@palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkspjwMACgkQ+gerLs4ltQ4mggCg090UYuKxFt2WH5iuiQJvqtbT
yMwAoNPvKEhj2xKhWiribWNT+j7/LBUa
=k4US
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to