[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-06 Thread R. David Murray
R. David Murray added the comment: Python3 is easier to do unicode in for programs that start with a clear bytes/string split. Yes, porting from python2 has bumps arising from the places where bytes and string are blurred. Yes if we could redo python3 knowing what we know now we could improv

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-06 Thread Christian Tanzer
Christian Tanzer added the comment: > If you can suggest ways of improving the string support without > breaking existing python3 code that may be using it (most likely > wrongly, but working for them), then I will happily review them. At the moment, I'm mainly interested in having code that run

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-05 Thread R. David Murray
R. David Murray added the comment: I agree that the situation is not the best, but it is the one we have. I can't delete those methods now, they've existed in Python3 for too long, and initially were the only thing that worked (albeit only with ASCII only strings). If you can suggest ways

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-05 Thread Christian Tanzer
Christian Tanzer added the comment: > Yes, the port from python2 to python3 of the email package > was...suboptimal. > ... > The whole concept of using unicode as a 7bit data channel only is > just...weird. +100 to both. > But, we are now stuck with maintaining that API for backward > compatibi

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-04 Thread R. David Murray
R. David Murray added the comment: Yes, the port from python2 to python3 of the email package was...suboptimal. (I wasn't a contributor when that happened, and the person who did it simply did not have time to do the needed rewrite...he had to settle for just making it more-or-less work.) The

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-04 Thread Christian Tanzer
Christian Tanzer added the comment: R. David Murray wrote at Wed, 04 Nov 2015 15:36:27 +: > There is no problem with supporting both 2.7 and python3 with the same > email API as long as your input strings are ASCII only, which is what > is required by the email RFCs (as I said, they do not s

[issue25545] email parsing docs need to be clear that only ASCII strings are supported

2015-11-04 Thread R. David Murray
R. David Murray added the comment: There is no problem with supporting both 2.7 and python3 with the same email API as long as your input strings are ASCII only, which is what is required by the email RFCs (as I said, they do not support unicode...even the new one only supports utf8 (a unicode