[issue27445] Charset instance not passed to set_payload()

Claude Paroz added the comment: Thanks for pushing the patch! -- ___ Python tracker <http://bugs.python.org/issue27445> ___ ___ Python-bugs-list mailing list Unsub

[issue27445] Charset instance not passed to set_payload()

Changes by Claude Paroz : -- keywords: +patch Added file: http://bugs.python.org/file43614/issue27445.diff ___ Python tracker <http://bugs.python.org/issue27

[issue27445] Charset instance not passed to set_payload()

New submission from Claude Paroz: In issue #16324, I contributed an improvement so as MIMEText __init__ accept Charset instances, not only encoding strings. The use case is from Django where we customize the Charset.body_encoding before passing it to the MIMEText initialization

[issue25955] email.utils.formataddr does not support RFC 6532

Changes by Claude Paroz : -- nosy: +claudep ___ Python tracker <http://bugs.python.org/issue25955> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16679] Wrong URL path decoding

Claude Paroz added the comment: Thanks for the explanations (and history). I realize that changing the behaviour is probably not an option. As an example in a framework, we are currently discussing how we will cope with this in Django: https://code.djangoproject.com/ticket/19468 On the

[issue16679] Wrong URL path decoding

Claude Paroz added the comment: I may understand your reasoning when you cannot make any assumptions about the encoding of a series of bytes. I think that the case of PATH_INFO is different, because it should comply with standards, and then you *can* make the assumption that the original path

[issue16679] Wrong URL path decoding

Claude Paroz added the comment: Attached are my proposed changes. Also, I just came across http://bugs.python.org/issue3300, which finally led Python urllib.parse.quote to default to UTF-8 encoding, after a lengthy discussion. -- keywords: +patch Added file: http://bugs.python.org

[issue16679] Wrong URL path decoding

New submission from Claude Paroz: In wsgiref/simple_server.py (WSGIRequestHandler.get_environ), Python 3 is currently populating the env['PATH_INFO'] variable by decoding the URL path, assuming it was encoded with 'iso-8859-1', which appears to be wrong, according t

[issue16324] MIMEText __init__ does not support Charset instance

Changes by Claude Paroz : -- keywords: +patch Added file: http://bugs.python.org/file27726/issue16324-1.diff ___ Python tracker <http://bugs.python.org/issue16

[issue16324] MIMEText __init__ does not support Charset instance

Claude Paroz added the comment: It's fine for me to consider it as an enhancement. The fix might be as simple as replacing **{'charset': _charset} by **{'charset': str(_charset)} in MIMEText __init__. -- ___ Python tracker

[issue16324] MIMEText __init__ does not support Charset instance

New submission from Claude Paroz: When initializing a MIMEText instance, it might be desirable to set the _charset parameter to a real Charset instance, not only a charset identifier (for example to pass a Charset with customized body_encoding). Unfortunately, this is failing: File