prepends the exception's module name to non-builtin exceptions, like
the interpreter itself does.

broke a number of doctests. should be discussed before checking in (see
discussion on python-dev).

exception's module name to non-builtin exceptions, like the interpreter
itself does.

bsddb.*open() methods cachesize parameter wouldn't work (raised an
internal bsddb.db exception when it was given).  The set_cachesize
call needed to be moved from the DB object to the DBEnv since the env
was introduced to allow for threading.

(will backport to 2.4)

Using None for a filename with the 'n' flag when calling bsddb.btopen
would cause an error while checking if the file None existed.  error
not likely to be seen as anyone using None for a filename would likely
use the 'c' flag in the first place.

https://sourceforge.net/tracker/?func=detail&atid=532154&aid=1467852&group_id=71702

pointer dereferences.

Mention ASCII as default encoding; update TODO list; use PyCF_ONLY_AST by MvL's suggestion; typographical tidying of MvL's name

in dicts and sets when computing the total number of references.

e.g. SimpleXMLRPCServer wasn't in here yet.

Wrapped in a try/except.

Add tests for the output of the TextCalendar and HTMLCalendar classes.

"O" arguments, so must not decref them.  This accounts
for why running test_contextlib.test_main() in a loop
eventually tried to deallocate Py_None.

report failures, we'll see.

Skip certain hopeless tests: compiler and logging.

compiler will likely always show varying leaks since it doesn't work
on a defined set of modules unless -u compiler is specified.  But that
takes forever (we only run with -u network currently).

logging causes hangs when running with -R.

Add tests for generator expressions too.

code work with C++ compilers.

with the getstring() results in pattern_subx. Will come back to that.

compile.c to add a cast.

still has errors from the casts of asdl_seq_GET to cmpop_ty, but
otherwise it's C++ clean.

for the bogus failure.

[x for x in it if x if x], were broken for no good reason by the PEP 308
patch.

to avoid confusing situations like:

>>> int("")
ValueError: invalid literal for int():
>>> int("2\n\n2")
ValueError: invalid literal for int(): 2

2

Also report the base used, to avoid:

ValueError: invalid literal for int(): 2

They now report:

>>> int("")
ValueError: invalid literal for int() with base 10: ''
>>> int("2\n\n2")
ValueError: invalid literal for int() with base 10: '2\n\n2'
>>> int("2", 2)
ValueError: invalid literal for int() with base 2: '2'

(Reporting the base could be avoided when base is 10, which is the default,
but hrm.) Another effect of these changes is that the errormessage can be
longer; before, it was cut off at about 250 characters. Now, it can be up to
four times as long, as the unrepr'ed string is cut off at 200 characters,
instead.

No tests were added or changed, since testing for exact errormsgs is (pardon
the pun) somewhat errorprone, and I consider not testing the exact text
preferable. The actually changed code is tested frequent enough in the
test_builtin test as it is (120 runs for each of ints and longs.)

StreamHandler now checks explicitly for None before using sys.stderr as the stream (see SF bug #1463840).

interpolate PY_FORMAT_SIZE_T for refcount display
instead of casting refcounts to long.

I understand that gcc on some boxes delivers
nuisance warnings about this, but if any new ones
appear because of this they'll get fixed by magic
when the others get fixed.