--with-dbm-liborder option doesn't know about sqlite

[doko42]

Bug report

Bug description:

As far as I can see, the --with-dbm-liborder option doesn't know about sqlite, and configuring without it defaults to

checking for --with-dbmliborder... gdbm:ndbm:bdb

Lib/dbm/init.py however mentions sqlite ...

_names = ['dbm.sqlite3', 'dbm.gnu', 'dbm.ndbm', 'dbm.dumb']

Am I reading that wrong, and sqlite isn't yet supported as an implementation for the dbm module?

CPython versions tested on:

3.14, 3.15

Operating systems tested on:

No response

[aisk]

Am I reading that wrong, and sqlite isn't yet supported as an implementation for the dbm module?

SQLite is an implementation of the dbm module, so I think this should be classified as a build bug.

I checked that --with-dbmliborder only affects which C library the _dbm module is built against, but sqlite3's build is specified by another option. So maybe we can treat this as a documentation improvement to the configure chapter, to clarify this option only affects the dbm modules' build, not the implementation selection order?