--with-dbm-liborder option doesn't know about sqlite
Open
Nobody has claimed this yet.
build
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how --with-dbm-liborder is handled during CPython configuration and compare it with the implementation order in Lib/dbm/init.py, especially dbm.sqlite3. Verify whether sqlite is intended to participate in the configured order; done means the option and the dbm implementation behavior agree about sqlite support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- build-system, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100