bpo-40837: Fix email.utils.encode_rfc2231(string, None, None)#20564
bpo-40837: Fix email.utils.encode_rfc2231(string, None, None)#20564spaceone wants to merge 1 commit intopython:mainfrom
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
@spaceone , please sign the CLA and we will need a bugs.python.org issue number. |
|
|
This PR is stale because it has been open for 30 days with no activity. |
|
@ezio-melotti why did you remove the CLA Signed label? |
jeah, lol. No merge since 6 years. |
encode_rfc2231() must not change the returned value if no transformation of the input was done.
This is also mentioned in the docstring of that function.
Actual behavior:
encode_rfc2231('foo bar', None, None)
'foo%20bar'
Expected behavior:
encode_rfc2231('foo bar', None, None)
'foo bar'
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
encode_rfc2231()must not change the returned value if no transformation of the input was done.This is also mentioned in the docstring of that function.
Actual behavior:
Expected behavior:
https://bugs.python.org/issue40837