(original) (raw)
On Tue, Apr 15, 2008 at 11:49 PM, "Martin v. L�wis" <martin@v.loewis.de> wrote:
My point is it will ignore this error, because the programmer didn't even know about the return value.
So it will possibly use data. But, it's all in the bug report and I'm only repeating myself.
I didn't recognize that we discussed this phrase. Sorry if I wasted your time.
Regards,
Ralf
> so, still: sorry no, the application should not just look at the resultIf it doesn't want to lose data, it \*has\* to, because of the way it's
> being returned.
currently implemented. There is no other way (other than ignoring the
error) in Python 2.5.x and earlier.
My point is it will ignore this error, because the programmer didn't even know about the return value.
So it will possibly use data. But, it's all in the bug report and I'm only repeating myself.
I never debated that. I debated whether that is a "rather severe" issue,
> The mmap.flush method should be fixed.
which I still don't think it is.
I didn't recognize that we discussed this phrase. Sorry if I wasted your time.
Regards,
Ralf