which sometimes seems to result in different terminology. It does
seem to be mostly compatible, though.

get terminology resources. Unfortunately there doesn't seem to be any
application I can ask for the basic StdSuites terminology (?).
- Prefer OSX-native versions of applications over OS9 versions.

something I don't understand, but for now ignore this.

Output the file name such that it cannot contain non-ascii characters.

has actually entered its event loop. As a stopgap, allow for a 10 second
grace period.

backport candidate

This is a first step towards regenerating the modules with newer, MacOSX,
versions of these programs, and using the programmatic interface to
get at the terminology in stead of poking in resource files.

code. This makes it a lot easier to compare the generated code for two
different versions of the suite.
- Various tweaks to the code to generate suites without looking at resource
files manually.

At the moment does little more than testing that the modules import
correctly and some classes can be instantiated.

Clean up section headings; make the bars on the left less fat.
Adjust the display of properties slightly.
Don't show stuff inherited from the base 'object' type.

    sys.modules previously produced an exception).

we try to manually launch the application and send it an ascr/gdte
event to get its terminology.

i.e. get_content_maintype() and get_content_subtype().

Also, add True, False for Python 2.2.x where x < 2 compatibility.

i.e. get_content_maintype() and get_content_subtype().

Adds a single function to improve generated bytecode.  Has a single line
attachment point, so it is completely de-coupled from both the compiler
and ceval.c.

Makes three simple transforms that do not require a basic block analysis
or re-ordering of code.  Gives improved timings on pystone, pybench,
and any code using either "while 1" or "x,y=y,x".

    Make sure we aren't masking any errors raised in tempfile.mkdtemp() by
    referencing the (then) unbound local 'dir'.

"Hereby I make the script in question available under the terms and
conditions of the latest Python License."

generalize to take a callback function and a void * data argument.
This might come in handy later... :-)

in normal cases, and also in error cases.

Bugfix candidate.

the foreground.

Arranged that all the objects exposed by __builtin__ appear in the list
of all objects.  I basically peed away two days tracking down a mystery
leak in sys.gettotalrefcount() in a ZODB app (== tons of code), because
the object leaking the references didn't appear in the sys.getobjects(0)
list.  The object happened to be False.  Now False is in the list, along
with other popular & previously missing leak candidates (like None).
Alas, we still don't have a choke point covering *all* Python objects,
so the list of all objects may still be incomplete.

dump empty TODO comment

Will backport.