BIND 10 #2043: Fix remaining Python warnings about unclosed files and sockets
BIND 10 Development
do-not-reply at isc.org
Thu Jun 14 21:08:04 UTC 2012
#2043: Fix remaining Python warnings about unclosed files and sockets
-------------------------------------+-------------------------------------
Reporter: muks | Owner:
Type: defect | Status: new
Priority: low | Milestone: New
Component: Unclassified | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
File and socket objects must be explicitly closed with `.close()` when
done using them, otherwise they generate warnings (and depending on the
interpreter, may be destroyed much later than expected, keeping the
underlying fd alive).
As part of bug #1828, we fixed many of these warnings. There are still a
few non-obvious ones left. There are also some which have been introduced
since the time when the trac1828 branch was created.
This is a new bug to fix those issues.
--
Ticket URL: <https://bind10.isc.org/ticket/2043>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list