[issue25545] email parsing docs: clarify that only ASCII strings are supported

2019-04-26 Thread immerrr again
immerrr again added the comment: Oh, wow, confusing indeed, but in historical context it makes slightly more sense. Thank you for the explanation! -- ___ Python tracker ___

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2019-04-26 Thread R. David Murray
R. David Murray added the comment: This is one of the infelicities of the translation of the old API to python3: 'get_payload(decode=True)' actually means 'give me the bytes version of this payload", which in this case is the utf-8, which is what you got. get_payload() means "give me the pay

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2019-04-25 Thread immerrr again
immerrr again added the comment: Hi everyone, It's the first time I'm using this bugtracker, so apologies in advance if I manage to break something from the first go. Not sure if it's the right place to report this, but I have the following repro that involves email.message_from_bytes: In [

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2018-12-05 Thread R. David Murray
R. David Murray added the comment: The problem comes from thinking you can parse an arbitrary email message if it is in unicode form. *YOU CANNOT DO THAT* in the general case (ie: non-ascii attachments). That said, the new email package API is designed to facilitate "off label" uses. I wo

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2018-12-05 Thread Jason R. Coombs
Jason R. Coombs added the comment: I don't think this ticket should be implemented as described. Consider the use-case in importlib_metadata, which loads metadata from a package, metadata known to be of a specified encoding. It already knows the encoding and has decoded the full message to t

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2015-11-07 Thread R. David Murray
R. David Murray added the comment: Issuing a warning is an interesting idea. Basically, deprecate using a non-ASCII string with message_from_string etc formally by issuing a deprecation warning as well as the doc note. -- ___ Python tracker

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2015-11-07 Thread John Mark Vandenberg
John Mark Vandenberg added the comment: Could it issue a UnicodeWarning? -- nosy: +John.Mark.Vandenberg ___ Python tracker ___ ___ Pyt

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2015-11-07 Thread R. David Murray
R. David Murray added the comment: Except that that might break code that is currently working, so I can't do that, even though I'd like to. -- ___ Python tracker ___ __

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2015-11-07 Thread Christian Tanzer
Christian Tanzer added the comment: Terry J. Reedy wrote at Fri, 06 Nov 2015 22:49:57 +: > email parsing docs: clarify that only ASCII strings are supported If that is the decision, `message_from_string` should raise an exception if it gets a non-ASCII argument! -- ___

[issue25545] email parsing docs: clarify that only ASCII strings are supported

2015-11-06 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- title: email parsing docs need to be clear that only ASCII strings are supported -> email parsing docs: clarify that only ASCII strings are supported ___ Python tracker _