[Patches] Optional list.append behavior
Christian Tismer
tismer@tismer.com
Mon, 13 Mar 2000 17:24:50 +0100
Guido van Rossum wrote:
> 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:
...
> 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()).
I will check these.
However: It would not hurt at all to do the error check
like now, but embrace it with an
if (PyThreadState_GET()) {
...
}
and otherwise simply forget about the object, since we are
finalizing anyway.
But I'll check these conditions and see if any action is necessary
at all.
ciao - chris
--
Christian Tismer :^) <mailto:tismer@appliedbiometrics.com>
Applied Biometrics GmbH : Have a break! Take a ride on Python's
Kaunstr. 26 : *Starship* http://starship.python.net
14163 Berlin : PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF
we're tired of banana software - shipped green, ripens at home