➜

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 serhiy.storchaka
Recipients ezio.melotti, serhiy.storchaka, vstinner
Date 2020-01-30.12:04:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580385892.89.0.367003869761.issue39500@roundup.psfhosted.org>
In-reply-to
Content 
Other examples are:

* PyObject_HasAttr
* PyObject_HasAttrString
* PyMapping_HasKey
* PyMapping_HasKeyString

They are bad examples, but can't be changed for backward compatibility. I wonder whether PyUnicode_IsIdentifier should also kept unchanged for backward compatibility.

There is also a number of *_Check functions which always succeeds.

Other example is _PyUnicode_EqualToASCIIString where the behavior is intentional.

PyUnicode_IsIdentifier() was not documented before. It makes easier to change its behavior.
History
Date User Action Args
2020-01-30 12:04:52serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, ezio.melotti
2020-01-30 12:04:52serhiy.storchakasetmessageid: <1580385892.89.0.367003869761.issue39500@roundup.psfhosted.org>
2020-01-30 12:04:52serhiy.storchakalinkissue39500 messages
2020-01-30 12:04:52serhiy.storchakacreate