[Patches] Optional list.append behavior

[Guido van Rossum]

> About the recursive delete: I'm about to make SLP 1.1
> available and would like to wait until that other patch
> is in. But I'm a bit worrying about the error handling
> code that I added. The error handling enforces the
> existence of tstate. Didn't we find out that it doesn't
> exist on finalization? Do I need to check tstate for
> NULL, maybe?

Oops.

I can't reproduce this however.  I created a 100000-nested tuple that
contained an object at the bottom to print "bye".  It got deleted
correctly when I exited.  I think only very few things are deleted
after the tstate is deleted...  The stuff that gets called by these:


	_PyBuiltin_Fini_2();
	PyMethod_Fini();
	PyFrame_Fini();
	PyCFunction_Fini();
	PyTuple_Fini();
	PyString_Fini();
	PyInt_Fini();
	PyFloat_Fini();
	PyGrammar_RemoveAccelerators(&_PyParser_Grammar);
	call_ll_exitfuncs();
	_Py_ResetReferences();

I don't have the time right now to inspect all these for destruction
of user objects; most seem to get rid of free lists only
(e.g. PyTuple_Fini()).

--Guido van Rossum (home page: http://www.python.org/~guido/)