Missleading example of value validation for `dbm` since 3.13
Open
Nobody has claimed this yet.
3.13
3.14
3.15
docs
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Documentation
Is not correct since sqlite is default backend. int will be silently stored and those who rely on dbm to validate the value are in trouble.
Linked PRs
- gh-137972
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
Open Doc/library/dbm.rst at lines 132-134 and review the value-validation example in light of sqlite being the default backend since Python 3.13. Update the example so it does not imply that dbm validates values in that configuration, then review linked PR gh-137972 to determine the current state of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100