r72147 - peps/trunk/pep-0383.txt
![](https://secure.gravatar.com/avatar/8ac615df352a970211b0e3d94a307c6d.jpg?s=120&d=mm&r=g)
Author: martin.v.loewis Date: Thu Apr 30 11:24:24 2009 New Revision: 72147 Log: Add more discussion. Modified: peps/trunk/pep-0383.txt Modified: peps/trunk/pep-0383.txt ============================================================================== --- peps/trunk/pep-0383.txt (original) +++ peps/trunk/pep-0383.txt Thu Apr 30 11:24:24 2009 @@ -104,7 +104,10 @@ get converted back to bytes with the python-escape error handler also. Encoding the data with the locale's encoding and the (default) strict error handler will raise an exception, encoding them with UTF-8 -will produce non-sensical data. +will produce non-sensical data. + +Data obtained from other sources may conflict with data produced +by this PEP. Dealing with such conflicts is out of scope of the PEP. For most applications, we assume that they eventually pass data received from a system interface back into the same system @@ -134,6 +137,11 @@ python-escape, there are required byte sequences which cannot be generated from replacement Unicode. +A few alternative approaches have been proposed: + +* create a new string subclass that supports embedded bytes +* use different escape schemes, such as escaping with a NUL + character, or mapping to infrequent characters. References ==========
participants (1)
-
martin.v.loewis