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 serhiy.storchaka
Recipients serhiy.storchaka
Date 2015-04-04.11:12:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Proposed patch fixes two related issues in a number of modules.

1. close() methods sometimes release multiple resources. Every closing operation can fail, but it shouldn't prevent releasing other resources. See for example issue21802.

2. close() should be idempotent. I.e. calling close() second times shouldn't have any effect. Even if close() failed, repeated call of close() (usually in __exit__(), in __del__(), or in finally block) shouldn't raise an exception.

Many close() methods already satisfy these conditions, but not all.
Date User Action Args
2015-04-04 11:13:01serhiy.storchakasetrecipients: + serhiy.storchaka
2015-04-04 11:13:00serhiy.storchakasetmessageid: <>
2015-04-04 11:13:00serhiy.storchakalinkissue23865 messages
2015-04-04 11:12:59serhiy.storchakacreate