Message246569
The obvious fix seems to be to not use splitlines but explicitly split on the allowed characters for ASCII based protocols and formats that only want \r and \n to be considered.
I don't think we can rightfully change the unicode splitlines behavior. |
|
Date |
User |
Action |
Args |
2015-07-10 16:59:23 | gregory.p.smith | set | recipients:
+ gregory.p.smith, barry, ezio.melotti, r.david.murray, martin.panter, serhiy.storchaka, demian.brecht, scharron |
2015-07-10 16:59:23 | gregory.p.smith | set | messageid: <1436547563.06.0.433849291939.issue22233@psf.upfronthosting.co.za> |
2015-07-10 16:59:23 | gregory.p.smith | link | issue22233 messages |
2015-07-10 16:59:22 | gregory.p.smith | create | |
|