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 martin.panter
Recipients Bruno Oliveira, The Compiler, benjamin.peterson, berker.peksag, doerwalter, lemburg, martin.panter, reaperhulk, serhiy.storchaka
Date 2015-10-01.02:35:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443666952.91.0.950971601367.issue25270@psf.upfronthosting.co.za>
In-reply-to
Content
The patch looks sufficient to fix the problem, though I do like Serhiy’s suggestions.

For the record, because I was curious: Function codecs.escape_encode() is not documented, and barely tested. It was used for the documented “string_escape” codec in Python 2, but this codec was removed for Python 3 in revision bc90fc9b70b7. The function was apparently added to support pickling, but I don’t see any evidence that it was ever used. Only the decode counterpart was used. I wonder if the encode function could be removed at some point.
History
Date User Action Args
2015-10-01 02:35:53martin.pantersetrecipients: + martin.panter, lemburg, doerwalter, benjamin.peterson, berker.peksag, serhiy.storchaka, The Compiler, reaperhulk, Bruno Oliveira
2015-10-01 02:35:52martin.pantersetmessageid: <1443666952.91.0.950971601367.issue25270@psf.upfronthosting.co.za>
2015-10-01 02:35:52martin.panterlinkissue25270 messages
2015-10-01 02:35:52martin.pantercreate