Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your 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 your contribution, we look forward to reviewing it!

CLA Submitted.

Got all checks to pass. Ready for review.

@eamanu Bumping this because it's been a while.

bumping again, and adding some details here.

To quote myself from the bug ticket:

cp874 != ibm_874 != iso_8859_11

What I can say is that the current cp874 is the implementation of the windows_874 code page. The page itself references the microsoft code page, and also contains the appropriate characters (like EURO SIGN).

https://github.com/python/cpython/blob/master/Lib/encodings/cp874.py
""" Python Character Mapping Codec cp874 generated from 'MAPPINGS/VENDORS/MICSFT/WINDOWS/CP874.TXT' with gencodec.py.

https://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP874.TXT

It seems appropriate to at least alias windows_874 with cp874. They are provably the same.

@malemburg please review or tap another.

I'll also throw a bump in here - the email's contentmanager dies pretty frequently from this encoding being missing. For now I'm getting around this with this, nabbed from https://bugs.python.org/issue17254

    aliases = encodings.aliases.aliases
    additional = {
        'windows_874': 'cp874'
    }
    aliases.update(additional)

@malemburg @ezio-melotti @csabella
I've updated the commit to meet current pipeline checks and standards.
Please let me know if there is anything else I can do.

I'm looking forward to squashing this years long bug. In my work writing python email parsers, we definitely saw this from Thai senders using Microsoft email clients.

Thanks!