Antoine Pitrou <pit...@free.fr> added the comment:
> static int
> _textiowrapper_clear(textio *self)
> {
> if (self->ok && _PyIOBase_finalize((PyObject *) self) < 0)
> return -1;
>
> This shows something scary: During a GC run, it is possible to invoke
> the "close()" method on a textio object. This is dangerous, and
> probably not allowed at all.
How is it scary? This is not worse than invoking a __del__ method.
> Returning -1 from a tp_clear() slot has no particular meaning, and the
> return value appears to be ignored by gcmodule.c
I don't think this is a problem.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8212>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
