[issue19539] The 'raw_unicode_escape' codec buggy + not apropriate for Python 3.x

Changes by Serhiy Storchaka : -- components: -Library (Lib) nosy: -serhiy.storchaka stage: -> needs patch type: -> enhancement versions: -Python 3.2, Python 3.5 ___ Python tracker _

[issue19539] The 'raw_unicode_escape' codec buggy + not apropriate for Python 3.x

Jan Kaliszewski added the comment: Which means that the description "Produce a string that is suitable as raw Unicode literal in Python source code" is (in Python 3.x) no longer true. So, if change/removal is not possible because of internal significance of the codec, I believe that the descri

[issue19539] The 'raw_unicode_escape' codec buggy + not apropriate for Python 3.x

Serhiy Storchaka added the comment: The 'raw_unicode_escape' codec can't be neither removed nor changed because it is used in pickle protocol. Just don't use it if its behavior looks weird for you. Right way to decode raw_unicode_escape-encoded data is use 'raw_unicode_escape' decoder. If a

[issue19539] The 'raw_unicode_escape' codec buggy + not apropriate for Python 3.x

New submission from Jan Kaliszewski: It seems that the 'raw_unicode_escape' codec: 1) produces data that could be suitable for Python 2.x raw unicode string literals and not for Python 3.x raw unicode string literals (in Python 3.x \u... escapes are also treated literally); 2) seems to be bug