[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Inada Naoki added the comment: bpo-33671 fixed this. -- resolution: -> fixed stage: test needed -> resolved status: open -> closed versions: +Python 3.8 -Python 3.7 ___ Python tracker

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Serhiy Storchaka added the comment: Could you please provide any benchmarks Tyler? -- nosy: +serhiy.storchaka ___ Python tracker

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

INADA Naoki added the comment: How about increasing default value to 32KiB or 64KiB too? binutils's cp works well for most cases, while it doesn't have option to specify blocksize. I want Python's copy functions works nice enough for common cases too. binutils cp uses 128KiB block for normal

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Raymond Hettinger added the comment: This seems reasonable to me. -- nosy: +rhettinger ___ Python tracker ___

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Changes by Terry J. Reedy : -- nosy: +terry.reedy stage: -> test needed type: -> enhancement ___ Python tracker ___

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Changes by Mariatta Wijaya : -- components: +Library (Lib) ___ Python tracker ___

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

Changes by Tyler Goodlet : -- pull_requests: +288 ___ Python tracker ___ ___

[issue29659] Expose the `length` arg from shutil.copyfileobj for public use

New submission from tyler: It would be handy to be able to pass the `length` default argument defined by `shutil.copyfileobj()` to other public functions througout the module. When copying very large files (1GB +), increasing the memory buffer can divide the copy time in half and currently