This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author yunlee
Recipients aldwinaldwin, barry, maxking, r.david.murray, yunlee
Date 2019-08-01.17:51:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALYHgxs6Roy4ghHQD-zw4ravP3u_F1o5+pET8q32NhFc_ymfMg@mail.gmail.com>
In-reply-to <1564663321.83.0.209773547758.issue37532@roundup.psfhosted.org>
Content
Hi, David:

I don't think your argument stands here. The whole world does not just
include English speaking countries. There are Spanish, Russian, Chinese,
etc. Any legacy packages should support all languages instead of just
English. This is definitely a bug in this package. I hope that the python
support team should fix this issue or simply add the "support English only"
description in the function explicitly . Otherwise it is very annoying for
other countries to use this package.

Thanks!
Yun

On Thu, Aug 1, 2019 at 5:42 AM R. David Murray <report@bugs.python.org>
wrote:

>
> R. David Murray <rdmurray@bitdance.com> added the comment:
>
> The input header is not valid (non-ascii is not allowed in headers), so
> you shouldn't expect make_header to do anything sensible.  Note that this
> is the legacy API, which is a toolkit and does not hold your hand when it
> comes to RFC compliance.  Aside from any other concerns, this is long
> standing behavior (it is the same in python2), and it doesn't make sense to
> change the behavior of a legacy API.
>
> ----------
> resolution:  -> not a bug
> stage: patch review -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue37532>
> _______________________________________
>
History
Date User Action Args
2019-08-01 17:51:55yunleesetrecipients: + yunlee, barry, maxking, aldwinaldwin
2019-08-01 17:51:55yunleelinkissue37532 messages
2019-08-01 17:51:55yunleecreate