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 lemburg
Recipients Rayologist, erlendaasland, lemburg
Date 2022-02-09.09:36:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <7f85873b-9ec0-92d6-1fda-f8afb4ee32c5@egenix.com>
In-reply-to <1644317665.3.0.667883627707.issue46662@roundup.psfhosted.org>
Content
On 08.02.2022 11:54, Erlend E. Aasland wrote:
> 
> The sqlite3 timestamp converter is buggy, as already noted in the docs[^1]. Adding timezone support is out of the question[^2][^3][^4][^5], but fixing it to be able to discard any attached timezone info _may_ be ok; at first sight, I don't see how this could break existing applications (like, for example adding time zone support could do). I need to think it through.

I think it's better to deprecate these converters and let users implement
their own.
History
Date User Action Args
2022-02-09 09:36:34lemburgsetrecipients: + lemburg, erlendaasland, Rayologist
2022-02-09 09:36:33lemburglinkissue46662 messages
2022-02-09 09:36:33lemburgcreate