GeezerVison

This is a performance critical function, please check that this has no slowdown on microbenchmark.

This is a performance critical function, please check that this has no slowdown on microbenchmark.

Do you have advises on how to write such benchmark?

Benchmarks on similar functions:

• os.read(): gh-129813, PEP 782: Use PyBytesWriter in posix extension #138829 (comment)
• io.FileIO.readall(): gh-129813, PEP 782: Use PyBytesWriter in _io.FileIO.readall #138901 (comment)

Creating a writer takes less than 30 ns, so time is dominated by I/O operations.

I wrote a similar change to use PyBytesWriter in socket.socket.recv(): #139097 (comment)

I am not worried about performance on this change. The more modern code (1) has the same complexity as the older code and (2) the CPU performance should already be dominated by the decryption that happens to generate the data being read in the first place - not our potential data copy if an internal resize were to move something.

Merged, thanks for reviews.