dgelessus 5c3bc5d7e5 Remove custom stream types and read all resource data upfront again ... The custom stream types were almost always slower than just reading the entire data into memory, and there's no reason not to do that - resources are small enough that memory usage and disk IO speed aren't a concern (at least not for any machine that's modern enough to run Python 3...). Perhaps the only performance advantage was when reading a small amount of data from the start of a compressed resource. In that case the custom stream could incrementally decompress only the part of the data that's actually needed, which was a bit faster than decompressing the entire resource and then throwing away most of the data. But this situation is rare enough that it's not worth handling in the rsrcfork library. If this is a real performance issue for someone, they can manually call the incremental decompression functions from rsrcfork.compress where needed.		2020-11-01 19:28:25 +01:00
..
compress	Remove custom stream types and read all resource data upfront again	2020-11-01 19:28:25 +01:00
__init__.py
__main__.py	Remove no longer needed type: ignore comment from .__main__	2020-11-01 19:13:11 +01:00
_io_utils.py	Remove custom stream types and read all resource data upfront again	2020-11-01 19:28:25 +01:00
api.py	Remove custom stream types and read all resource data upfront again	2020-11-01 19:28:25 +01:00
py.typed