tree 2d11f44c5184450b13f3d85336eba4f72be6cfa0
parent 0189c010c30d62147793057b83eb539592e117bd
author Guido van Rossum <guido@python.org> 917300173 +0000
committer Guido van Rossum <guido@python.org> 917300173 +0000
HG:extra convert_revision:svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/python/branches/legacy-trunk%4012446

There's a macro PycString_IMPORT which the documentation listed as
PycStringIO_IMPORT.  While arguably the name used in the documentation
is more consistent, I think it's probably safer not to change the
macro definition and instead fix the doco.