with uintptr_t (fix MSVC 5.0 build)

PyNode_Compile()), make sure that an exception is actually set --
otherwise someone stomped on our error.  [2.0 checkin of this fix.]

an exception set.  This shouldn't happen, but we see it at times...

  for excessive recursion.

participates in the "--root" hack, ie. it also has a new root directory
hacked on at the very last minute (essential if the .pth file is to be
included in an RPM or other smart installer!).

(allows the same FancyGetopt object to be used multiple times with different
option tables).

Small stylistic changes by VM:
- is_enabled() -> isenabled()
- static ... Py_<func> -> static ... gc_<func>

(except for : and volume:, where they are needed).

- Don't call both AC_CHECK_FUNCS and AC_REPLACE_FUNC for 'hypot', as the
latter already does everything the former does (because it's implemented as
a call to the former.)

- Don't call AC_CHECK_FUNC() without any 'action' clauses or with an action
clause that just defines HAVE_<function>. Instead, call AC_CHECK_FUNCS,
which defines 'HAVE_<function>' of itself, possibly with aditional 'action'
clauses.

No checks are removed by this patch, only moved around, and some duplicates
are removed.

weeks.

-32768..65535 is acceptable. Added B specifier (with values from
-128..255). No L added (which would have completed the set) because l
already accepts any value (and the letter L is taken for quadwords).

  wasn't actually used anywhere.
Drop the "from xxx_util import*" backwards compability hacks.

python20_d.lib) only active on MSVC++; different library formats needed
for different compilers, and it's handled by the Distutils anyways.

and so forth.

(is bgen still "still under development"?)

based on bug report by Neil Schemenauer

fix com_call_function to cope with trailing comma in "f(a, b,)"

python-dev discussion.

This should catch future version incompatibilities on Windows.  Alas,
this doesn't help for 1.5 vs. 1.6; but it will help for 1.6 vs. 2.0.

to signify a test that should be marked as 'skipped' rather than 'failed'.
Also 'document' it, in README.

Honesty's the best policy.

mark the test as 'skipped', rather than 'failed'.

at all (my computer doesn't have a Sound Blaster), this doesn't mean
there's a bug in linuxaudiodev. The only error the test suite skips
is currently ImportError -- so that's what we raise. If you see a problem
with this patch, say so and I'll retract. If you think raising an ImportError
sucks, you're right -- but I ain't gonna buy a SB and I sure ain't gonna
let the test-suite fail on my machine.

Ensure that # of args to sprintf always matches # of format specifiers.

snprintf() is available.