Brett Cannon added the comment: First off, that assertEquals should have a custom error message stating what values the date objects had to better tell how off things were.
Second, this can probably be solved by upping the timedelta to something like a minute or something for when it's run on a really slow machine (I mean the test itself is wonky based on the the definition of date.today() and not being able to freeze time, so being upwards of a minute off should be acceptable to verify it's still "today"). ---------- nosy: +brett.cannon _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15933> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
