Missleading example of value validation for `dbm` since 3.13

[koutoftimer]

Documentation

cpython/Doc/library/dbm.rst

Lines 132 to 134 in 9558d22

	# Storing a non-string key or value will raise an exception (most
	# likely a TypeError).
	db['www.yahoo.com'] = 4

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.

[eendebakpt]

On 3.13+ indeed the assignment db['www.yahoo.com'] = 4 does not throw error. The value is assigned and stored as a bytes object.

The docs could be changed to something like "... can raise an exception, depending on the backend ...". But I am a little surprised the difference in backends is there in the first place. The documentation at https://docs.python.org/3/library/dbm.html states the keys and values are stored as bytes, but not which kind of objects can be assigned.

@erlend-aasland