➜

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 lemburg
Recipients Bruno Oliveira, The Compiler, benjamin.peterson, berker.peksag, doerwalter, lemburg, martin.panter, reaperhulk, serhiy.storchaka
Date 2015-10-01.07:34:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <560CE1FC.4030409@egenix.com>
In-reply-to <1443666952.91.0.950971601367.issue25270@psf.upfronthosting.co.za>
Content 
On 01.10.2015 04:35, Martin Panter wrote:
> 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.

It's a codec, so either we remove both functions or leave both
functions in. It's still used in pickletools and serves a useful
purpose there (to unescape embedded escapes in byte streams).
History
Date User Action Args
2015-10-01 07:34:36lemburgsetrecipients: + lemburg, doerwalter, benjamin.peterson, berker.peksag, martin.panter, serhiy.storchaka, The Compiler, reaperhulk, Bruno Oliveira
2015-10-01 07:34:36lemburglinkissue25270 messages
2015-10-01 07:34:36lemburgcreate