[issue13793] hasattr, delattr, getattr fail with unnormalized names

Changes by Benjamin Peterson : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13793] hasattr, delattr, getattr fail with unnormalized names

Raymond Hettinger added the comment: I concur with Benjamin on all counts. -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bug

[issue13793] hasattr, delattr, getattr fail with unnormalized names

Benjamin Peterson added the comment: Because it's (very) expensive and the method you propose would fail in the case that someone had put the normalized and unnormalized string in the object's __dict__. -- ___ Python tracker

[issue13793] hasattr, delattr, getattr fail with unnormalized names

Jim Jewett added the comment: Why is normalization in getattr unacceptable? I won't pretend to *like* it, but the difference between two canonically equal strings really is (by definition) just a representational issue. Would it be OK to normalize in object's own implementation, so that cust

[issue13793] hasattr, delattr, getattr fail with unnormalized names

Benjamin Peterson added the comment: Normalizing the string in getattr() is unacceptable. We'll just have to document, that all identifiers are in NFKC. -- ___ Python tracker _

[issue13793] hasattr, delattr, getattr fail with unnormalized names

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list

[issue13793] hasattr, delattr, getattr fail with unnormalized names

New submission from Jim Jewett : The documentation for hasattr, getattr, and delattr state that they are equivalent to object.attribute access; this isn't quite true, because object.attribute uses a NFKC-normalized version of the string as only the secondary location, while hasattr, getattr, a