Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
> what about simply excluding TPFLAGS_MAPPING from PySequence > and TPFLAGS_Sequence from PyMapping? It will remove the types > that are 100% not sequences or mappings, as these flags > are mutually exclusive by definition. This is more plausible than the proposed breaking change. > The result will be much more accurate If they can't be made fully reliable, why would we ever recommend that someone use these functions in real code? They can be made to guess better than they guess now, but there is still guesswork. ISTM developers should follow the structure pattern matching implementation and refuse the temptation to guess. If a class declares itself as a mapping or sequence, that is reliable information. In contrast, these functions attempt to divine meaning in the absence of a clear declaration. Using these functions will likely result in subtle bugs. Once Py_TPFLAGS_MAPPING and Py_TPFLAGS_SEQUENCE became available, we should have deprecated these functions. No one should use them anymore. Their core design is flawed; they tried to deduce semantics from structural artifacts. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46376> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
