Message346273
Victor, I think you misunderstood the issue. The problem is not that a decoding error is raised. The problem is that the incremental decoder no longer raises where it raised before.
I think that both behavior may be correct, and that it is better to not rely on ability of the incremental decoder with final=False to detect an invalid encoded data, but I see now that it is possible to fix for the original issue more carefully, without changing that behavior. PR 14304 does this.
It also change the UTF-16 incremental decoder with the surrogatepass error handler to return a non-empty data when decode a low surrogate with final=False. It is not necessary, but it makes all UTF-* decoders consistent and makes tests simpler. |
|
Date |
User |
Action |
Args |
2019-06-22 10:11:05 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, vstinner, ezio.melotti, methane, RalfM, xtreak, roufique7 |
2019-06-22 10:11:05 | serhiy.storchaka | set | messageid: <1561198265.14.0.141412799426.issue24214@roundup.psfhosted.org> |
2019-06-22 10:11:05 | serhiy.storchaka | link | issue24214 messages |
2019-06-22 10:11:04 | serhiy.storchaka | create | |
|