an OverflowError instead of a TypeError to be consistent
with "%c" % 256. See SF patch #710127.

the Standard_Suite, but various other suites do expect it (the Finder
implements get() without declaring it itself). It is probably another
case of OSA magic. Adding them to the global base class.

within a certain context. Give them an _Prop_ prefix, so they don't
accidentally obscure an element from another suite (as happened with
the Finder). Comparisons I'm not sure about, so I left them as global
names.

Also got rid of the lists if declarations, they serve no useful purpose.

- Added a --dump option that doesn't generate the module but dumps
  the pretty-printed aete resource(s) on stdout.

instead of raising a TypeError. (From SF patch #710127)

Add tests to verify this is fixed.

Add various tests for '%c' % int.

you to say something like "talker.count(want=Address_Book.people)" in
stead of having to manually create the aetypes.Type(Address_Book.people.want)
OSA type.

and initialize the event loop (if not done previously) to work around
a bug (IMHO) in MacOSX 10.2.

the primary name.

be sorted after the main name, otherwise filling of properties and
elements messes up.

Sorting is always more difficult than expected:-)

separating space or not between encoded chunks.  Closes SF bug
#710498.

platforms which have dup(2).  The makefile() method is built directly on top
of the socket without duplicating the file descriptor, allowing timeouts to
work properly.  Includes a new test case (urllibnet) which requires the
network resource.

Closes bug 707074.

remains to be done.

to the ExpectedSkips class.  Add test_scriptpackages to Mac only list.
Add test_unicode_file to Windows only list.

Will backport to 2.2.

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

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.

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).

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().