Message274593
Victor, it seems the only option here (other than closing this as won't fix) is to modify the UTF-16 decoder in 2.7 to allow lone surrogates, which would be consistent with the UTF-8 and UTF-32 decoders. While it's too late to enforce strict compliance in 2.7, it shouldn't hurt to expand the domain of acceptable encodings. Then if surrogates are always passed in 2.7, a silently ignored "surrogatepass" handler could be added for compatibility with 3.x code. |
|
Date |
User |
Action |
Args |
2016-09-06 18:34:13 | eryksun | set | recipients:
+ eryksun, vstinner, ezio.melotti, xiang.zhang, lazka |
2016-09-06 18:34:13 | eryksun | set | messageid: <1473186853.38.0.910017694825.issue27971@psf.upfronthosting.co.za> |
2016-09-06 18:34:13 | eryksun | link | issue27971 messages |
2016-09-06 18:34:13 | eryksun | create | |
|