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 bar.harel
Recipients aganders3, aviramha, bar.harel, benjamin.peterson, brandtbucher, bukzor, georg.brandl, levkivskyi, methane, miss-islington, pitrou, rhettinger, serhiy.storchaka
Date 2022-01-15.09:28:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642238911.49.0.547361734883.issue46376@roundup.psfhosted.org>
In-reply-to
Content
> That was true in 2011 and it is still true today

Python's methodology greatly shifted since 2011. For the better or worse, Python lost some of its duck typing. Nowadays, most people use linters. Wherever you'd try to pass sre_parse.SubPattern, the linter will throw an error saying it's not a Sequence even if it fully behaves like one. You can silence that error but you'll continue receiving such warnings all over the code, whether in stdlib or out in the wild. The meaning of Sequence now shifted to "inherits from abc.Sequence". The only thing wrong with PySequence_Check is that the ecosystem shifted, but its view of a Sequence remained the same.
History
Date User Action Args
2022-01-15 09:28:31bar.harelsetrecipients: + bar.harel, georg.brandl, rhettinger, pitrou, benjamin.peterson, methane, bukzor, aganders3, serhiy.storchaka, levkivskyi, miss-islington, brandtbucher, aviramha
2022-01-15 09:28:31bar.harelsetmessageid: <1642238911.49.0.547361734883.issue46376@roundup.psfhosted.org>
2022-01-15 09:28:31bar.harellinkissue46376 messages
2022-01-15 09:28:31bar.harelcreate