Charlie Marsh cedd2e0b3f Use a buffered reader for wheel metadata (#1082) ... ## Summary It turns out this is significantly faster when reading (e.g.) _just_ the `METADATA` file from a zipped wheel. I audited other `File::open` usages, and everything else seems to be using a buffered reader already (directly, or in whatever third-party crate it's passed to) _or_ is read immediately in full. See the criterion benchmark: ``` file_reader/numpy-1.26.3-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl time: [6.9618 ms 6.9664 ms 6.9713 ms] Found 4 outliers among 100 measurements (4.00%) 4 (4.00%) high mild file_reader/flask-3.0.1-py3-none-any.whl time: [237.50 µs 238.25 µs 239.13 µs] Found 7 outliers among 100 measurements (7.00%) 3 (3.00%) high mild 4 (4.00%) high severe buffered_reader/numpy-1.26.3-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl time: [648.92 µs 653.85 µs 660.09 µs] Found 4 outliers among 100 measurements (4.00%) 3 (3.00%) high mild 1 (1.00%) high severe buffered_reader/flask-3.0.1-py3-none-any.whl time: [39.578 µs 39.712 µs 39.869 µs] Found 8 outliers among 100 measurements (8.00%) 3 (3.00%) high mild 5 (5.00%) high severe ```		2024-01-24 15:22:55 -05:00
..
src	Use a buffered reader for wheel metadata (#1082)	2024-01-24 15:22:55 -05:00
Cargo.toml	Remove some unused dependencies (#1077)	2024-01-24 11:58:21 -05:00