Cliff Wells wrote: > This appears to be a bug in SA 0.4.2p3: > > >>From the datetime docs: > ''' > Note: In order to stop comparison from falling back to the default > scheme of comparing object addresses, datetime comparison normally > raises TypeError if the other comparand isn't also a datetime object. > However, NotImplemented is returned instead if the other comparand has a > timetuple attribute. > ''' > > It appears to me (although I need to do some more digging to verify) > that types.DateTime lacks a timetuple attribute, so a TypeError is > getting raised rather than returning NotImplemented.
There is now support for comparisons with datetimes on the left-hand-side in r4113. (RHS has always worked.) -j --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
