Jaakko Moisio added the comment:
The new patch is fine as it is, but my logic behind using err_flag was the
following: err_flag was set solely based on the inspection of return value of
fwrite and ferror, without referencing to errno. It is of course true that at
the same time errno is set to
Jaakko Moisio added the comment:
> The test pass with Python 3 which does not use the "FILE*" API
> anymore. So you should maybe migrate to Python 3 :-)
Yes. I will eventually. But not all the libraries I'm using are migrated yet.
--
Added file: http://bugs
Jaakko Moisio added the comment:
> I tried to reply to the review of my last patch but this tracker
> software itself crashed. Is there anyone who would be interested in
> the traceback?
Never mind. I found the meta tracker and posted my traceb
Jaakko Moisio added the comment:
I tried to reply to the review of my last patch but this tracker software
itself crashed. Is there anyone who would be interested in the traceback?
Anyway, I'll reply here.
On 2013/05/15 08:37:29, Charles-François Natali wrote:
> http://bugs.python.or
Changes by Jaakko Moisio :
Added file: http://bugs.python.org/file30266/fileobject-fix4.patch
___
Python tracker
<http://bugs.python.org/issue17976>
___
___
Python-bug
Jaakko Moisio added the comment:
> Yeah, would you like to write a patch?
Yes. It's fileobject-fix3.patch attached to this issue record.
--
Added file: http://bugs.python.org/file30262/fileobject-fix3.patch
___
Python tracke
Jaakko Moisio added the comment:
Thank you for your comments.
> I was a little surprised when Jaako says that ferror() is enough to
> detect this, so I modified Serhiy code to print ferror(), and actually
> ferror() reports an error for subsequent writes, not for the first one
&g
New submission from Jaakko Moisio:
file.write doesn't sometimes raise IOError when it should, e.g. writing to
/dev/full in line buffered mode:
jaakko@jm-laptop:~$ python
Python 2.7.5+ (2.7:a32a3b79f5e8, May 14 2013, 14:20:11)
[GCC 4.7.2] on linux2
Type "help", "copy
