[issue10016] shutil.copyfile -- allow sparse copying

2020-11-06 Thread Irit Katriel
Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue10016] shutil.copyfile -- allow sparse copying

2018-06-12 Thread Giampaolo Rodola'
Change by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10016] shutil.copyfile -- allow sparse copying

2016-12-07 Thread Samuel Shapiro
Samuel Shapiro added the comment: Patch fails on CentOS 6 -- python 2.6 [root@LG-E1A-LNX python2.6]# patch --dry-run -l -p1 -i shutil-2.6.patch shutil.py patching file shutil.py Hunk #1 succeeded at 22 (offset 1 line). Hunk #2 succeeded at 52 with fuzz 1 (offset 1 line). Hunk #3 FAILED at 61.

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-04 Thread Tarek Ziadé
Changes by Tarek Ziadé ziade.ta...@gmail.com: -- assignee: - tarek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10016 ___ ___ Python-bugs-list

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-04 Thread Tom Potts
Tom Potts karake...@gmail.com added the comment: @pitrou Hmm... the online docs and the contents of the doc directory on the trunk branch say differently: Resize the stream to the given *size* in bytes (or the current position if *size* is not specified). The current stream position isn't

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-04 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Ok, after experimenting, I now understand what the truncate() call is for. However, your heuristic for detecting sparse files is wrong. The unit for st_blocks is undefined as per the POSIX standard, although it gives recommendations: “The unit

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-04 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: By the way: Thanks for your comments -- I'm trying to put together some unit tests and documentation, against the Subversion trunk. Please ignore trunk; all development (new features) should be done against branches/py3k. --

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-03 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: The use of fdst.truncate() is indeed wrong, since truncate() in 3.x is defined as truncating up to the current file position (which has been moved forward by the latest seek()). -- nosy: +pitrou ___

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-02 Thread Tom Potts
New submission from Tom Potts karake...@gmail.com: Copying a sparse file under Linux using shutil.copyfile will not result in a sparse file at the end of the process. I'm submitting a patch that will remedy this. Note that I am only concerned with Linux at the moment -- as far as I know this

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-02 Thread Tom Potts
Tom Potts karake...@gmail.com added the comment: (see opening message) -- Added file: http://bugs.python.org/file19108/shutil-2.7.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10016

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-02 Thread Tom Potts
Changes by Tom Potts karake...@gmail.com: Added file: http://bugs.python.org/file19109/shutil-3.2.1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10016 ___

[issue10016] shutil.copyfile -- allow sparse copying

2010-10-02 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: You are right that this needs to be tested on other platforms. In order to so test it (and in any case!), the patch will need unit tests. It also needs doc updates. In general patch itself looks good to me, modulo the concern you