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 ferringb
Recipients ferringb
Date 2012-01-15.04:29:21
SpamBayes Score 5.165188e-06
Marked as misclassified No
Message-id <1326601765.34.0.310008166629.issue13788@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-01-15 04:29:25ferringbsetrecipients: + ferringb
2012-01-15 04:29:25ferringbsetmessageid: <1326601765.34.0.310008166629.issue13788@psf.upfronthosting.co.za>
2012-01-15 04:29:24ferringblinkissue13788 messages
2012-01-15 04:29:23ferringbcreate