CP273.TXT to be used with gencodec.py. Enables Communication with "old" IBM Mainframes 

Logged In: YES user_id=38388 Can you provide a reference of where and how this encoding is used ? We also need information of where the attached file originated. Thanks.

Logged In: YES user_id=1074928 The encoding is used on IBM Mainframes here in Germany and Austria. Mostly on "old" VM/VSE Machines. Rawdata is transferred via MQSeries and then encoded from "cp273" to "latin_1". The file has been translated from the original IBM RFC by myself. www.unicode.org has no equivalent file on their FTP-Servers (ftp://ftp.unicode.org/Public/MAPPINGS/). CP273 is an alias for this charset. source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Regards Michael 

 Given that the patch author has provided further details, can this patch be accepted now? 

 I guess so. Note that it's not a patch, but the template to be used with gencodec.py. 

 Yes the patch can be included. The file should be used by gencodec.py

Looks like it was never included. I guess '"old" IBM Mainframes' is a dwindling user base, should this one be closed?

A Google search for "cp273 encoding" reveals that at least one other person needed it: http://www.stroeder.com/pylib/encodings/cp273.py

"Old IBM Mainframes" are widely used in the financial industry. It would be good if the patch is included

Like I said a few years: this can go in. Python is used a lot in the financial industry. The code page is referenced in this RFC: http://rfc.dotsrc.org/rfc/rfc1345.html This page has a good comparison of the various IBM code pages as shipped with different tools (jdk, glibc, aix, etc.): http://www.haible.de/bruno/charsets/conversion-tables/RFC1345-IBM.html

I tried figuring out to rebuild the codecs using the scripts in Tools/unicode/ but failed. Is the use of that directory documented anywhere?

A.M. Kuchling wrote: > > A.M. Kuchling <lists@amk.ca> added the comment: > > I tried figuring out to rebuild the codecs using the scripts in Tools/unicode/ but failed. Is the use of that directory documented anywhere? See the Makefile in that directory - that's what I use to build the codecs. If you just want to create a single codec, have a look at the gencodec.py module doc-string.

The consensus is that this should have gone into Python years ago.

New changeset 7d9d1bcd7d18 by Andrew Kuchling in branch 'default': #1097797: Add CP273 codec, and exercise it in the test suite http://hg.python.org/cpython/rev/7d9d1bcd7d18

New changeset fa2581bbef44 by Andrew Kuchling in branch 'default': Add news entry for #1097797; whitespace cleanup http://hg.python.org/cpython/rev/fa2581bbef44

Committed this to 3.4.

New changeset 93645b0b6750 by Andrew Kuchling in branch 'default': #1097797: add the original mapping file http://hg.python.org/cpython/rev/93645b0b6750

In changeset d843a1caba78 (I screwed up the issue number in the commit), I added aliases according to http://lists.w3.org/Archives/Public/ietf-charsets/2002JulSep/0153.html plus what appears to be the conventional alias of just the number, and added it to the codecs docs, making a wild guess based on the issue title that the Language is German.