bpo-40423: Optimization: use close_range(2) if available (GH-22651)
close_range(2) should be preferred at all times if it's available, otherwise we'll use closefrom(2) if available with a fallback to fdwalk(3) or plain old loop over fd range in order of most efficient to least. [note that this version does check for ENOSYS, but currently ignores all other errors] Automerge-Triggered-By: @pablogsal
K
Kyle Evans committed
1800c600801709958af66bebfa683a4e7570810f
Parent: c230fde
Committed by GitHub <noreply@github.com>
on 10/11/2020, 8:18:53 PM