[issue43436] bounded _lru_cache_wrapprer behaves as if typed=True when it wasn't

New submission from Dan Snider : Isn't the point of setting typed=True to make it so that e.g. True doesn't register as a hit when there is already a cache entry for 1.0? Assuming that is the case, although this report specifically targets 3.8 I found no indication that what I believe is the

[issue43436] bounded _lru_cache_wrapprer behaves as if typed=True when it wasn't

Change by Karthikeyan Singaravelan : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue43436] bounded _lru_cache_wrapprer behaves as if typed=True when it wasn't

Raymond Hettinger added the comment: Thanks for the report, but this isn't a bug. Setting typed=True guarantees that types are treated as distinct entries. Setting typed=False means that the implementation MAY ignore the type and only use equality, but it is not required to do so. If it is