Uh oh!
There was an error while loading. Please reload this page.
bpo-39040: added whitespaced to linesep_splitter in email.policy - #17590
bpo-39040: added whitespaced to linesep_splitter in email.policy#17590manfred-kaiser wants to merge 1 commit into
Conversation
the-knights-who-say-ni
commented
Dec 13, 2019
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). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
bitdancer
commented
Dec 13, 2019
As noted in the issue this fix is incorrect. |
I'm working on a mailfilter in python and used the method "get_filename" of the "EmailMessage" class.
In some cases a wrong filename was returned. The reason was, that the Content-Disposition Header had a line break and the following intention was interpreted as part of the filename.
After fixing this bug, I was able to get the right filename.
https://bugs.python.org/issue39040
I had to change "linesep_splitter" in "email.policy" to match the intention.
Old Value:
linesep_splitter = re.compile(r'\n|\r')New Value:
linesep_splitter = re.compile(r'\n\s+|\r\s+')https://bugs.python.org/issue39040