Here's the expression for my case
{IIF(CallSiteBinder(Convert($arg0).__eq__(Convert(Unbox($arg1, 0,
IIF(CallSiteBinder(op_LessThan(Convert($arg0),
Convert(Unbox($arg1, -1,
IIF(CallSiteBinder(op_GreaterThan(Convert($arg0),
Convert(Unbox($arg1, 1, IIF((Not(((coerceResult =
Convert($arg0)
Hi Keith,
On Thu, Mar 29, 2012 at 9:15 PM, Keith Rome wrote:
> I have a few questions about the contents of the NuGet packages for
> IronPython. They seem to be up-to-date since the current version listed is
> 2.7.2 from 3/13. It looks like JD Hardy is the “owner” of both
> distributions, but I a
First off just to make your life easier in the future the DebugView
property on the expression is much better than the other view - it produces
something that looks like C#.
Ok, I think the types are actually different and the LHS is succeeding on
one of ==, <, or >. I say that because in MakeS
The types that are being compared are as follows:
class CmpErr:
"Dummy element that always raises an error during comparison"
def __cmp__(self, other):
raise ZeroDivisionError
And an Int32. The bisect test creates a list of the CmpErr objects and
then tries to insert the number 10
