I am pretty much indifferent on TimeRange.always() is. The .is_always() function is just used in the fts extension to do a slight optimization in case the time range is irrelevant.
Regarding change of timestamp signature: What's the technical argument for breaking API (and breaking it in a big way)? -- TimeRange.always() is inconsistent https://bugs.launchpad.net/bugs/614295 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: There's an inconsistency in TimeRange.always() produced by ZG and libzg. ZG uses (-maxint, maxint), while libzg uses (0, maxint). This introduces incompabilities when using ZG's TimeRange.is_always(), where it'll return True for ZG's TimeRanges and False for libzg's TimeRanges. Our mightly leader Seif decided that ZG should also use (0, maxint), so this is a reminder to change it for the next release. _______________________________________________ Mailing list: https://launchpad.net/~zeitgeist Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp