zeitgeist team mailing list archive

[Siegfried Gevatter <rainct@xxxxxxxxxx>]

2010/8/6 Michal Hruby <michal.mhr@xxxxxxxxx>:
> Our mightly leader Seif decided that ZG should also use (0, maxint), so
> this is a reminder to change it for the next release.

I disagree, if we are using signed integers then "always" includes the
negatives one. (Another thing is whether it really makes sense to have
signed integers or we should switch to unsigned ones, which I think we
should do).

-- 
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.