➜

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 serhiy.storchaka
Date 2017-01-07.07:10:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483773006.32.0.276673146687.issue29190@psf.upfronthosting.co.za>
In-reply-to
Content 
PyUnicode_Compare() and PyUnicode_RichCompare() can raise an exception if one of arguments is not ready unicode object. The result is not always checked for error. Proposed patch gets rid of possible bugs. PyUnicode_Compare() and PyUnicode_RichCompare() in Modules/_pickle.c are replaced with _PyUnicode_EqualToASCIIString() and _PyUnicode_EqualToASCIIId() which never fail. Additional check is added in Modules/_decimal/_decimal.c to ensure that the string which is came from a user code is ready.

All other occurrences of PyUnicode_Compare() seems are called only with ready unicode objects.
History
Date User Action Args
2017-01-07 07:10:06serhiy.storchakasetrecipients: + serhiy.storchaka
2017-01-07 07:10:06serhiy.storchakasetmessageid: <1483773006.32.0.276673146687.issue29190@psf.upfronthosting.co.za>
2017-01-07 07:10:06serhiy.storchakalinkissue29190 messages
2017-01-07 07:10:06serhiy.storchakacreate