It's possible to create insane datetime objects by using the constructor
"backdoor" inserted for fast unpickling.  Doing extensive range checking
would eliminate the backdoor's purpose (speed), but at least a little
checking can stop honest mistakes.

Bugfix candidate.

when keep_blank_values is true.

off a new compiler wng under MSVC6).

the newly created tuples, but tuples added in the freelist are now cleared in
tupledealloc already (which is very cheap, because we are already
Py_XDECREF'ing all elements anyway).

Python should have a standard Py_ZAP macro like ZAP in pystate.c.

Fixes SF Bug #773356

[Part of patch #909005] Repeating exception changed from 'raise socket.error, why' to just raise.  Make use of connect_ex() raise socket.error with 2-tuple instead of just error code

(Reported by Matthias Klose)

Removed the entire __name__ == '__main__' block.

Modified string.split documentation to reflect behaviour of splitting emtpy string.  Closes SF bug #811604

NULL in case of error, but the functions are declared to return int.
MSVC 6 properly complains about that.  Return -1 on error instead.

Gives 30% speedup on "a,b=1,2" and 25% on "a,b,c=1,2,3".

automatically.

existent path.  Pointed out by jvr that entries could be non-file items for
custom importers.

for regex syntax.
Fixes bug #883604 .

isinstance() or issubclass() to the recursion limit of the interpreter.

Change %08l to %p to print a pointer.
Will backport to 2.3.

'a.extend(a)' isn't so special anyway.

I've been bitten by this myself in the past half year.
I hope this fix is right.
I'll backport this to 2.3.

UNTESTED!!!

This simple two-line patch has been sitting on SF for more than 2 years.
I'm guessing it's because nobody knows how to test it -- I sure don't.
It doesn't look like you can get to this part of the code on Unixish
or Windows systems, so the "how to test it?" puzzle has more than one
part.  OTOH, if this is dead code, it doesn't matter either if I just
broke it <wink>.