Issue 45858: Deprecate default converters in sqlite3

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/90016

classification

Title:	Deprecate default converters in sqlite3
Type:	behavior	Stage:
Components:	Library (Lib)	Versions:

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	Strongbeard, erlendaasland, ethan.furman, iafisher
Priority:	normal	Keywords:

Created on 2021-11-21 16:46 by iafisher, last changed 2022-04-11 14:59 by admin.

Messages (2)
msg406727 - (view)	Author: Ian Fisher (iafisher) *	Date: 2021-11-21 16:46
Per discussion at https://discuss.python.org/t/fixing-sqlite-timestamp-converter-to-handle-utc-offsets/, the default converters in SQLite3 have several bugs and are probably not worth continuing to maintain, so I propose deprecating them and removing them in a later version of Python. Since the converters are opt-in, this should not affect most users of SQLite3.
msg406728 - (view)	Author: Ian Fisher (iafisher) *	Date: 2021-11-21 16:47
See also bpo-26651 for a related proposal to deprecate the converter/adapter infrastructure entirely. The proposal in this bug is more limited: remove the default converters (though I think the default adapters should stay), but continue to allow users to define their own converters.