On May 7, 2010, at 9:30 AM, Iceberg wrote: > Right now, IS_DATE_IN_RANGE(minimum=foo, maximum=bar) does NOT accept > the given minimum nor maximum value. That is not the design intention > according to error message. Please get rid off the two equal marks in > IS_DATE_IN_RANGE.__call__(). > > Same applies to IS_DATETIME_IN_RANGE.
Anybody who patches this: please add the relevant doctests.