This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ammar2
Recipients SilentGhost, ammar2, belopolsky, paul.moore, pekka.klarck, r.david.murray, steve.dower, tim.golden, tim.peters, zach.ware
Date 2016-12-30.11:08:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've attached two patches that fix this behavior, one by simply foregoing the fold detection for this time range on windows (the patch that I'd argue is simpler and more readable)

And one that truncates the passed values to local to not be negative. This one would have been simple but unfortunately there's the complication that there are two local calls and additionally, the second one cannot be truncated to exactly 0 because then we incorrectly detect a fold for the timestamp 0.
Date User Action Args
2016-12-30 11:08:44ammar2setrecipients: + ammar2, tim.peters, paul.moore, belopolsky, tim.golden, r.david.murray, SilentGhost, pekka.klarck, zach.ware, steve.dower
2016-12-30 11:08:44ammar2setmessageid: <>
2016-12-30 11:08:44ammar2linkissue29097 messages
2016-12-30 11:08:43ammar2create