changes to the bsddb source.

Update all projects so Debug builds use "/Zi" instead of "/ZI", which means everything should still build under MSVC5

NOTE:  All these projects had messed-up line endings (but MSVC didnt mind).  Executing a diff with "--ignore-all-space" will show the specific changes, but I made a complete checkin with correct line endiings as it is the correct thing to do!

Include limits.h if we have it.

If we have stat.h include it if we don't have sys/stat.h

Include stat.h if needed; different Mac filename compare

CHAR_MAX, use hardcoded -128 and 127.  This may seem strange, unless
you realize that we're talking about signed bytes here!  Bytes are
always 8 bits and 2's complement.  CHAR_MIN and CHAR_MAX are
properties of the char data type, which is guaranteed to hold at least
8 bits anyway.

Otherwise you'd get failing tests on platforms where unsigned char is
the default (e.g. AIX).

Thanks, Vladimir Marangozov, for finding this nit!

what the dozen+ subprojects are for, which are and aren't
expected to build out of the box, and what else is needed to get
them all to build.  Also explained that Alpha configurations
don't refer to pre-beta, but to the Alpha processor!  That's
baffled me for years <0.7 wink>.

Test case for the pty module.

- fixed parser flag propagation (of all stupid bugs...)

more suitable.

   if the multiline flag isn't given.

we want to have GC enabled in the beta.

attempting a recursive import and causing a fatal error.

Someone who knows what they are doing needs to replace this with something
that makes sense -- I'm not running Windows right now.

This'll work fine with 2.0 or 1.5.2, but is less than ideal for
1.6a1/a2.  But the code to accomodate 1.6a1/a2 was released with
Distutils 0.9, so it can go away now.

Regression test for the new winreg.py module.

[Could a Windows person someone please review this?]