[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Roundup Robot added the comment: New changeset ef5aa8d7e932 by Georg Brandl in branch '3.3': Closes #12350: clarify blocks/block size members of stat result. http://hg.python.org/cpython/rev/ef5aa8d7e932 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: ope

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Roundup Robot added the comment: New changeset c32657e278f6 by Georg Brandl in branch '2.7': Closes #12350: clarify blocks/block size members of stat result. http://hg.python.org/cpython/rev/c32657e278f6 -- ___ Python tracker

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Martin Panter added the comment: What happened to this patch? The current documentation is very misleading because the descriptions of the two block fields appear to complement each other. -- nosy: +vadmium ___ Python tracker

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

R. David Murray added the comment: I think that wording is as good as we can do for now. Providing a way to determine the size of st_blocks blocks should be a separate issue (a feature request). That enhancement can include an update to these docs, but since it is an enhancement it will onl

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Lars Wirzenius added the comment: Right. So I guess at least the following should be changed (I'll make an actual patch once there's consensus): * st_blocks should say that the size of block is often 512 bytes, but that's not guaranteed, and there's no way to know for sure * st_blksize shoul

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Changes by R. David Murray : -- versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

R. David Murray added the comment: Ah, found it: Issue 10016. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

R. David Murray added the comment: Ah, bingo. That was what was tickling at my memory but I couldn't remember what the exact issue was I was recalling. I forget what I was doing where that mattered, but as I vaguely remember it there is no portable way to find out what blocksize st_blocks i

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

Lars Wirzenius added the comment: http://pubs.opengroup.org/onlinepubs/009695399/basedefs/sys/stat.h.html says "A file system-specific preferred I/O block size for this object. In some file system types, this may vary from file to file.", which says essentially the same as the Linux stat(2) m

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

R. David Murray added the comment: Looks good for linux. Do you have a posix reference that confirms this interpretation? -- nosy: +r.david.murray ___ Python tracker ___ _

[issue12350] Improve stat_result.st_blocks and st_blksize documentation

New submission from Lars Wirzenius : Attached patch adds a few words to the os.stat documentation for the st_blocks and st_blksize fields to clarify them. -- assignee: docs@python components: Documentation files: stat_result.patch keywords: patch messages: 138467 nosy: docs@python, liw