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 iafisher
Recipients MrFuppes, corona10, erlendaasland, iafisher
Date 2021-10-05.00:00:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Unfortunately fixing this will have to be considered a backwards-incompatible change, since Python doesn't allow naive and aware datetime objects to be compared, so if sqlite3 starts returning aware datetimes, existing code might break.

Alternatively, perhaps this could be fixed in conjunction with changing sqlite3's API to allow per-database converters and adapters. Then, the old global TIMESTAMP converter could be retained for compatibility with existing code, and new code could opt-in to a per-database TIMESTAMP converter with the correct behavior.
Date User Action Args
2021-10-05 00:00:22iafishersetrecipients: + iafisher, corona10, erlendaasland, MrFuppes
2021-10-05 00:00:22iafishersetmessageid: <>
2021-10-05 00:00:22iafisherlinkissue45335 messages
2021-10-05 00:00:22iafishercreate