[issue30588] Missing documentation for codecs.escape_decode

Serhiy Storchaka added the comment: Reading the stackoverflow questions, I am not sure that this function would be useful for the author of the question. He just needs to remove b'\\000', this is only what we know. There are many ways to do it, and after using codecs.escape_decode() you will

[issue30588] Missing documentation for codecs.escape_decode

Carl Bordum Hansen added the comment: You have a point, the function is not in codecs.__all__. Reading the stackoverflow questions, it seems like this is a function that is useful. -- nosy: +carlbordum ___ Python tracker

[issue30588] Missing documentation for codecs.escape_decode

Serhiy Storchaka added the comment: I disagree. We can change, rename or remove it because it is not public function and never was. But we can not just remove it while it is used in the pickle module, and there is no reason to change it as it works pretty good for its purpose. If you want t

[issue30588] Missing documentation for codecs.escape_decode

Change by Carl Bordum Hansen : -- keywords: +patch pull_requests: +14542 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/14747 ___ Python tracker __

[issue30588] Missing documentation for codecs.escape_decode

Change by Gregory P. Smith : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue30588] Missing documentation for codecs.escape_decode

Gregory P. Smith added the comment: We can't change it or remove it, it is public by virtue of its name. We should document it. Removing or renaming it to be _private requires a PendingDeprecationWarning -> DeprecationWarning -> removal cycle. it is well known and used. https://stackoverf

[issue30588] Missing documentation for codecs.escape_decode

Andrew Svetlov added the comment: -1 Internal function means: you can use it on your risk but the function can be changed or even removed in any Python release. I see no point in documenting and making it public. -- nosy: +asvetlov ___ Python track

[issue30588] Missing documentation for codecs.escape_decode

Paul Hoffman added the comment: Bumping this thread a bit. It appears that this "internal" function is being talked about out in the real world. I came across it in a recent blog post, saw that it wasn't in the official documentation, and went looking here. I propose that it be documented ev

[issue30588] Missing documentation for codecs.escape_decode

Matthieu Dartiailh added the comment: The issue is that unicode_escape will not properly handle strings mixing unicode character and escaped character as it assumes latin-1 compatible characters only. For example, given the literal string 'Δ\nΔ', one cannot encode using latin-1 and encoding it us

[issue30588] Missing documentation for codecs.escape_decode

Serhiy Storchaka added the comment: This is an internal function kept for compatibility. It is used only for decoding pickle protocol 0 data created in Python 2. Look at unicode_escape and raw_unicode_escape codecs for doing similar decoding to strings in Python 3. -- nosy: +serhiy.sto

[issue30588] Missing documentation for codecs.escape_decode

New submission from Matthieu Dartiailh: codecs.escape_decode does not appear in the codecs documentation. This function is to my knowledge the only convenient way to process the escaped characters in a literal string (actually found here https://stackoverflow.com/questions/4020539/process-esca