This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients efiop, eryksun, gregory.p.smith, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-07-01.13:17:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561987037.15.0.478912477476.issue37380@roundup.psfhosted.org>
In-reply-to
Content
> 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.
History
Date User Action Args
2019-07-01 13:17:17vstinnersetrecipients: + vstinner, gregory.p.smith, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, efiop
2019-07-01 13:17:17vstinnersetmessageid: <1561987037.15.0.478912477476.issue37380@roundup.psfhosted.org>
2019-07-01 13:17:17vstinnerlinkissue37380 messages
2019-07-01 13:17:16vstinnercreate