[ZCM] [ZC] 1843/ 3 Resolve "IISet.keys: bad exception handling"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1843 Update (Resolve) "IISet.keys: bad exception handling"
 Status Resolved, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/1843

==============================================================
= Resolve - Entry #3 by tim_one on Jul 18, 2005 3:36 pm

 Status: Accepted => Resolved

Turned out that Bucket_rangeSearch() was ignoring the error returns from its two calls to Bucket_findRangeEnd(), due to overly, umm, "compressed" coding.  This could also lead to a segfault, if you passed two arguments and the second was of a wrong type.  Repaired now, for ZODBs 3.2.10, 3.4.1, and 3.5.
________________________________________
= Assign - Entry #2 by tim_one on Jul 16, 2005 3:46 pm

 Status: Pending => Accepted

 Supporters added: tim_one


________________________________________
= Request - Entry #1 by d.maurer on Jul 16, 2005 12:34 pm


Uploaded:  "IISetKeys.bug"
 - http://www.zope.org/Collectors/Zope/1843/IISetKeys.bug/view
"BTrees.IIBTree.IISet.keys" does not return "NULL" in case its argument is of the wrong type.

Python may later report the exception "TypeError: expected integer key" from an unrelated location (which leads to great
confusion).
==============================================================