You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update shutil.rst to clarify copy performance on Windows #142407
Actually the shutil.copy2() used the Windows API COPYFILE2, which is faster, and native call which means don't copy to memory on userspace, and support copy-on-write.
So this should be mentioned in documention to let people know rather than only knowing until read all the opened issues on github and source code of shutil.
Related info:
how shutil was implemented: #7160.
why only shutil.copy2() use Windows API COPYFILE2 while shutil.copyfile() not: #137074.
data that shows shutil.copy2() or Windows API COPYFILE2 can accelerate transfer speed: https://github.com/antirotor/speedcopy.
PR of new version copy2 implemented: #105055.
Hello! This would be my first contribution to CPython.
I’d like to give this doc fix a try — is it okay if I work on it?
I plan to update the "Platform-dependent efficient copy operations" section in shutil.rst based on the info in this thread.
Activity
CodeSeeed commentedon Jan 31, 2026
Hello! This would be my first contribution to CPython.
I’d like to give this doc fix a try — is it okay if I work on it?
I plan to update the "Platform-dependent efficient copy operations" section in
shutil.rstbased on the info in this thread.Thank you!
gh-142407: Clarify copy performance on Windows in shutil docs (GH-142408
pythongh-142407: Clarify copy performance on Windows in shutil docs (p…
pythongh-142407: Clarify copy performance on Windows in shutil docs (p…