Giampaolo Rodola' g.rod...@gmail.com added the comment:
Closing out because no response has been provided by the OP.
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6768
Changes by Antoine Pitrou pit...@free.fr:
--
assignee: - giampaolo.rodola
stage: - needs patch
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6768
Giampaolo Rodola' g.rod...@gmail.com added the comment:
I'm not sure how to reproduce this issue but I doubt calling close() from
__del__ would solve the problem, neither would be a good idea as close() might
end up being called more than once, which is not desirable.
Try to paste the code
Changes by Giampaolo Rodola' billiej...@users.sourceforge.net:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6768
___
New submission from Daniel Keysers dkeys...@gmail.com:
I'm not very experienced in Python, but while tracking down an issue
with a too many open files error I think I found a missing resource
release in asyncore's file_wrapper. Since Rev. 64062 added the os.dup()
in __init__ this class reads
