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 berker.peksag
Recipients berker.peksag
Date 2016-12-31.17:41:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483206107.71.0.541035804461.issue29123@psf.upfronthosting.co.za>
In-reply-to
Content
======================================================================
FAIL: CheckSqlTimestamp (sqlite3.test.types.DateTimeTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/buildarea/3.6.angelico-debian-amd64/build/Lib/sqlite3/test/types.py", line 391, in CheckSqlTimestamp
    self.assertEqual(ts.year, now.year)
AssertionError: 2016 != 2017

----------------------------------------------------------------------

See http://buildbot.python.org/all/builders/AMD64%20Debian%20root%203.6/builds/93/steps/test/logs/stdio for details.

In Lib/sqlite3/test/types.py, there is a comment saying

    # SQLite's current_timestamp uses UTC time, while datetime.datetime.now() uses local time.

Unless I'm missing something, there is no reason not to use datetime.utcnow(). That would make the test more robust.
History
Date User Action Args
2016-12-31 17:41:47berker.peksagsetrecipients: + berker.peksag
2016-12-31 17:41:47berker.peksagsetmessageid: <1483206107.71.0.541035804461.issue29123@psf.upfronthosting.co.za>
2016-12-31 17:41:47berker.peksaglinkissue29123 messages
2016-12-31 17:41:47berker.peksagcreate