Message 138542 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	liw
Recipients	docs@python, liw, r.david.murray
Date	2011-06-17.18:42:09
SpamBayes Score	0.0010390142
Marked as misclassified	No
Message-id	<1308336130.2.0.102232281084.issue12350@psf.upfronthosting.co.za>
In-reply-to

Content
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 should say it is size of efficient I/O, and is unrelated to st_blocks Should there be something more? Ideally, there should be a way to find out the size of blocks for st_blocks, but I don't know how to figure that out (though probably code from GNU's du could be borrowed).

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 should say it is size of efficient I/O, and is unrelated to st_blocks

Should there be something more? Ideally, there should be a way to find out the size of blocks for st_blocks, but I don't know how to figure that out (though probably code from GNU's du could be borrowed).

History
Date	User	Action	Args
2011-06-17 18:42:10	liw	set	recipients: + liw, r.david.murray, docs@python
2011-06-17 18:42:10	liw	set	messageid: <1308336130.2.0.102232281084.issue12350@psf.upfronthosting.co.za>
2011-06-17 18:42:09	liw	link	issue12350 messages
2011-06-17 18:42:09	liw	create