I'm working on Bazaar (bzr) VCS. One of our user report about bug that occurs because of his Windows XP machine use cp720 codepage for DOS console. cp720 is OEM Arabic codepage.
Python standard library does not have encoding map for this encoding so I create corresponding one. Attached patch provide cp720.py file for encodings package and mention this encoding in documentation.

As a user I experienced this bug. With python 3.1, the interpreter
terminate with fatal error:
"Py_Initialize: can't initialize sys standard streams
LookupError: unknown encoding: cp720"
I think, this can be replicated by changing the active code page in the
cmd session, before invoking the interpreter. The following command will
do so:
> chcp 720
without the patch python would crash after this command.
I think testing the patch after this command is sufficient.

Instead of using another source of third-party files, I suggest to use the Windows
functions to generate the mapping.
The attached patch contains a script, genwincodec.py, which uses MultiByteToWideChar
and generates a codec file.
I use it like this:
.\PCBuild\python Tools\unicode\genwincodec.py 720 > Lib\encodings\cp720.py
The generated file is also in the patch.

Reconsidering, I'd like to ask for two changes:
- please record the command(s) used to generate tables on Windows
somewhere, in either Tools/unicode/Makefile, or a separate batch file.
- please arrange for the doc string of the generated file to identify
the source of the data base; in particular, make sure that the Windows
version on which this was run is identified. It might be that future
Windows versions change the mappings.

The codec file now starts with the comment:
"""Python Character Mapping Codec cp720 generated on Windows:
Vista 6.0.6002 SP2 Multiprocessor Free with the command:
python Tools/unicode/genwincodec.py 720
"""
I also added a file Tools\unicode\genwincodecs.bat that currently only
generates cp720.py.
Applied in r74000 (trunk) and r74003 & r74004 (py3k)