➜

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 pablogsal
Recipients Henrique Andrade, pablogsal
Date 2018-03-15.23:56:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521158169.01.0.467229070634.issue33081@psf.upfronthosting.co.za>
In-reply-to
Content 
The way is to delete the object. IMHO I would not say is "leaked" as the object is still alive and holds resources and these resources are properly handled on destruction.

I cannot think of an immediate use case of closing both file descriptors but not deleting the object.
History
Date User Action Args
2018-03-15 23:56:09pablogsalsetrecipients: + pablogsal, Henrique Andrade
2018-03-15 23:56:09pablogsalsetmessageid: <1521158169.01.0.467229070634.issue33081@psf.upfronthosting.co.za>
2018-03-15 23:56:09pablogsallinkissue33081 messages
2018-03-15 23:56:08pablogsalcreate