This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aviramha
Recipients aganders3, aviramha, bar.harel, benjamin.peterson, brandtbucher, bukzor, georg.brandl, levkivskyi, methane, miss-islington, pitrou, rhettinger, serhiy.storchaka
Date 2022-01-15.08:19:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642234775.16.0.426433087193.issue46376@roundup.psfhosted.org>
In-reply-to
Content
I agree that a developer should and would prefer the `Py_TPFLAGS_*` but when you visit https://docs.python.org/3/c-api/sequence.html
It seems like the best practice to determine Sequence protocol is by using this function, hence leading to confusion. There's no recommendation to use the new `Py_TPFLAGS_*`.
To have this knowledge of `Py_TPFLAGS_*` one should be very knowledgable in Python's C-API.
How about adding a deprecation note to `PyMapping_Check` & `PySequence_Check` in the documentation, suggesting the alternative path (to use `PyType_HasFeature`)?
History
Date User Action Args
2022-01-15 08:19:35aviramhasetrecipients: + aviramha, georg.brandl, rhettinger, pitrou, benjamin.peterson, methane, bukzor, aganders3, serhiy.storchaka, levkivskyi, bar.harel, miss-islington, brandtbucher
2022-01-15 08:19:35aviramhasetmessageid: <1642234775.16.0.426433087193.issue46376@roundup.psfhosted.org>
2022-01-15 08:19:35aviramhalinkissue46376 messages
2022-01-15 08:19:35aviramhacreate