incorrect % characters; characters outside the printable range are
 replaced with '?'

Added hash() and compare() functions. Needed because multiple WinObj's can now refer to the same underlying WindowRef.

Blacklisted a few constants with funny definitions (and they're not important anyway: backward compatible error numbers).

    using GNU libc's getline()

warnings in this same module, to prevent getting a warning about
importing regex (we *know* that it's obsolete :-).

use of PyErr_Warn()!  This module is a good guinea pig because it's
been obsolete since 1.5.0 was released.

so we can't use it.

While I'm at it, got rid of string module use.  (Found several new
hard special cases for a hypothetical conversion tool: from string
import join, find, rfind; and a local assignment "find=string.find".)

additional escape sequences defined for Unicode.
This closes bug #117158.

This closes bug #126034.

doesn't work.  Make it 0.  (Although it really *should* be 0 or +1 --
the refcount is incremented when it is raised as an exception, but not
otherwise.)

Add an XXX comment at the beginning expressing disappointment over the
confusing way refcount behavior of arguments is documented.

Get rid of BeOpen references.

exceptions but always print a warning message.

required to work around restrictions on the arguments of
u.translate():

1) don't pass the deletions argument if it's empty;

2) convert table to Unicode if s is Unicode.

This fixes SF bug #124060.

1) multi-char separator
2) multi-char separator that only occurs at last position
3) all of the above with mixed Unicode and 8-bit-string arguments

bugs #126161 and 123634).

The solution doesn't use the unicode-escape encoding; that has other
problems (it seems not 100% reversible).  Rather, it transforms the
input Unicode object slightly before encoding it using
raw-unicode-escape, so that the decoding will reconstruct the original
string: backslash and newline characters are translated into their
\uXXXX counterparts.

This is backwards incompatible for strings containing backslashes, but
for some of those strings, the pickling was already broken.

Note that SF bug #123634 complains specifically that cPickle fails to
unpickle the pickle for u'' (the empty Unicode string) correctly.
This was an off-by-one error in load_unicode().

XXX Ugliness: in order to do the modified raw-unicode-escape, I've
cut-and-pasted a copy of PyUnicode_EncodeRawUnicodeEscape() into this
file that also encodes '\\' and '\n'.  It might be nice to migrate
this into the Unicode implementation and give this encoding a new name
('half-raw-unicode-escape'? 'pickle-unicode-escape'?); that would help
pickle.py too.  But right now I can't be bothered with the necessary
infrastructural changes.

bugs #126161 and 123634).

The solution doesn't use the unicode-escape encoding; that has other
problems (it seems not 100% reversible).  Rather, it transforms the
input Unicode object slightly before encoding it using
raw-unicode-escape, so that the decoding will reconstruct the original
string: backslash and newline characters are translated into their
\uXXXX counterparts.

This is backwards incompatible for strings containing backslashes, but
for some of those strings, the pickling was already broken.

#125981: closing sockets was not thread-safe.

numbers" instead; we have not described "reals" anywhere else in the
documentation, and this is not the place to change the story!

Reported by Keith Briggs <keith.briggs@bt.com>.

open_flags which contains the flags supported by gdbm.  Closes patch
#102802.

Fix a small style consistency nit.

version of Python.  ;-(

with Python 1.5.2 for now.

did not include it in the signature.

Fixed some markup nits.

PySys_AddWarnOption().

PySys_AddWarnOption().