Message218597
This issue was mainly resolved in issue12892. The surrogatepass error handler now works with UTF-16* and UTF-32* encodings. But for other encodings it behaves as for UTF-8 (preserve old behavior). Should we change the behavior for non-UTF encodings end raise an exception (as for "strict")? |
|
Date |
User |
Action |
Args |
2014-05-15 07:26:14 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, loewis, vstinner, ezio.melotti, kennyluck |
2014-05-15 07:26:14 | serhiy.storchaka | set | messageid: <1400138774.55.0.515048816946.issue13916@psf.upfronthosting.co.za> |
2014-05-15 07:26:14 | serhiy.storchaka | link | issue13916 messages |
2014-05-15 07:26:14 | serhiy.storchaka | create | |
|