Quoting from the SQLite docs:
"It is recommended that extension loading be enabled using the SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION method rather than this interface, so the load_extension() SQL function remains disabled. This will prevent SQL injections from giving attackers access to extension loading capabilities."

Suggesting to make sqlite3.Connection.enable_load_extension a module level function, and use sqlite3_db_config() iso. sqlite3_enable_load_extension(). We could add an optional argument for also enabling the SQL function.

1. Introduce sqlite3.enable_load_extension(enable, /, enable_sql_api=False)
2. Add deprecation warning to sqlite3.Connection.enable_load_extension()
3. In Python 3.12, remove sqlite3.Connection.enable_load_extension()

> We could add an optional argument for also enabling the SQL function.

Actually, using sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION, ...) can only enable the C API, not the SQL API, so adding an optional argument to sqlite3.enable_load_extension() makes no sense.

> Suggesting to make sqlite3.Connection.enable_load_extension a module level function

This actually needs to be a sqlite3.Connection method, thus altering the behaviour of the current function.

Attached patch alters the behaviour of sqlite3.Connection.enable_load_extension() to never enabling the SQL API.

This may require a deprecation period and a warning since it's a change in behaviour, but since enable_load_extention() is not enabled by default, we can perhaps do without the warning?