2010/8/6 Mikkel Kamstrup Erlandsen <mikkel.kamst...@gmail.com>:
> Regarding change of timestamp signature: What's the technical argument
> for breaking API (and breaking it in a big way)?

I don't really think we should break it now (just saying that it'd
make more sense, but in practice I don't think it'll make a

TimeRange.always() is inconsistent
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     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to