Re: [Zeitgeist] [Bug 614295] [NEW] TimeRange.always() is inconsistent

2010-08-06 Thread Siegfried Gevatter
2010/8/6 Michal Hruby : > 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 si

[Zeitgeist] [Bug 614295] [NEW] TimeRange.always() is inconsistent

2010-08-06 Thread Michal Hruby
Public bug reported: 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