[issue33572] False/True as dictionary keys treated as integers

Change by Terry J. Reedy : -- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python ___ Python tracker ___ __

[issue33572] False/True as dictionary keys treated as integers

Tim Peters added the comment: I expect these docs date back to when ints, longs, and floats were the only hashable language-supplied types for which mixed-type comparison could ever return True. They could stand some updates ;-) `fractions.Fraction` and `decimal.Decimal` are more language-s

[issue33572] False/True as dictionary keys treated as integers

Terry J. Reedy added the comment: Mark, are you suggesting a doc addition (and a change of Components) or should we close this as 'not a bug'? -- nosy: +terry.reedy ___ Python tracker ___

[issue33572] False/True as dictionary keys treated as integers

Mark Dickinson added the comment: It's documented here: https://docs.python.org/3/library/stdtypes.html#mapping-types-dict > Numeric types used for keys obey the normal rules for numeric > comparison: if two numbers compare equal (such as 1 and 1.0) then > they can be used interchangeably to

[issue33572] False/True as dictionary keys treated as integers

Janusz Harkot added the comment: Python 3.6.5 (default, Mar 29 2018, 03:28:50) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. >>> dta = {False: 'false', True: 'true', 0: 'zero', 1: 'one'} >>> print(dta[False]) zero >>> dta {False: 'zero', Tru

[issue33572] False/True as dictionary keys treated as integers

New submission from Janusz Harkot : using boolean (True/False) as dictionary keys, coerce them to integers - is this behavior documented somewhere? I know that asking to fix this is not easy fix, but shouldn't this be highlighted everywhere with red flags and warnings, so people will know that