[issue19050] [Python 2, Windows] fflush called on pointer to potentially closed file

[STINNER Victor]

STINNER Victor added the comment:

> This snippet let my interpreter crash immediately

Well, I don't understand the issue. If you write a bug, Python crashes. Ok, so? Please fix your bug. Don't expect Python from recovering from any bug.

The io stack of Python 3 is safer because it has a direct control on file descriptors, whereas Python 2 io stack relies on the C library "stdio.h".

I suggest to close this issue as "wontfix" and add it to the long list of "Bugs in the C stdio (used by the Python I/O)":
https://haypo-notes.readthedocs.org/python.html#bugs-in-the-c-stdio-used-by-the-python-i-o

----------
title: fflush called on pointer to potentially closed file -> [Python 2, Windows] fflush called on pointer to potentially closed file

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19050>
_______________________________________