New submission from Ferringb <ferri...@gmail.com>:
The current implementation of closerange essentially is a bruteforce invocation
of close for every integer in the range.
While this works, it's rather noisy for stracing, and for most invocations, is
near a thousand close invocations more than needed.
As such it should be aware of /proc/${PID}/fd, and use that to isolate down
just what is actually open, and close that.
----------
components: Extension Modules
files: closerange-optimization.patch
keywords: patch
messages: 151273
nosy: ferringb
priority: normal
severity: normal
status: open
title: os.closerange optimization
type: performance
Added file: http://bugs.python.org/file24241/closerange-optimization.patch
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13788>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
