Message193647
Unless I'm misunderstanding something, the current implementation does match the current documentation: if <buffer-size> < n, returning <buffer-size> bytes is returning "up to n". "Up to" means it could be "less than".
So you are advocating a change in behavior...but I believe there is a reason read1 is implemented the way it is, so I suspect that isn't going to happen. Probably what you want to do is change the buffer size when you open the file so that it is greater than your 'n'. |
|
Date |
User |
Action |
Args |
2013-07-24 14:00:58 | r.david.murray | set | recipients:
+ r.david.murray, pitrou, benjamin.peterson, stutzbach, nikratio, hynek, serhiy.storchaka |
2013-07-24 14:00:58 | r.david.murray | set | messageid: <1374674458.15.0.800403559799.issue18524@psf.upfronthosting.co.za> |
2013-07-24 14:00:58 | r.david.murray | link | issue18524 messages |
2013-07-24 14:00:57 | r.david.murray | create | |
|