STINNER Victor <vstin...@redhat.com> added the comment:
> The example is just emulating a problem from someone else's code that's > closing our handle. Typically this situation occurs because the code is > holding onto a handle value for a kernel object (File, Section, Job, Process, > Thread, Event, etc) that got closed. Without accessing private attributes, I don't see how someone can discover the private handle. So for me, it's more a serious bug in an application, no? Blindly closing random handles doesn't sound like a good idea to me. > The handle value eventually gets reused, such as for our _handle. That's a side effect on the blindly closing random handles. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37380> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
