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

[Eryk Sun]

Change by Eryk Sun :


--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Tal Einat]

Tal Einat  added the comment:

I agree this should probably be ignored for security-only branches.  However, 
AFAIK 2.7 is still in bugfix status, not security-only.  If there's interest, 
I'm happy to build with AMK's fix on 2.7 on Windows to see if it works, and if 
so provide a PR.

--
nosy: +taleinat

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[ppperry]

Change by ppperry :


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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com