➜

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 2016-11-26.15:48:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480175314.71.0.35688135657.issue28808@psf.upfronthosting.co.za>
In-reply-to
Content 
PyUnicode_CompareWithASCIIString() never set an exception in 3.2 and earlier versions. Since 3.3 it sets an exception and returns -1 if the first argument is not ready Unicode object, but this was not documented until issue28701. Due to undocumenting this behavior many (if not all) callers don't check whether it returned an error.

Proposed patch restores old behavior of PyUnicode_CompareWithASCIIString().
History
Date User Action Args
2016-11-26 15:48:34serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, ezio.melotti
2016-11-26 15:48:34serhiy.storchakasetmessageid: <1480175314.71.0.35688135657.issue28808@psf.upfronthosting.co.za>
2016-11-26 15:48:34serhiy.storchakalinkissue28808 messages
2016-11-26 15:48:34serhiy.storchakacreate