Charles-François Natali neolo...@free.fr added the comment:
Martin, is there any reason not to commit your patch?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14433
___
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 2de5e9715fe9 by Martin v. Löwis in branch '3.2':
Issue #14433: Prevent msvcrt crash in interactive prompt when stdin is closed.
http://hg.python.org/cpython/rev/2de5e9715fe9
New changeset 2c27093fd11f by Martin v.
Martin v. Löwis mar...@v.loewis.de added the comment:
Out of the original report, ISTM that:
a) the exit of the interpreter on closing stdin is considered correct behavior,
and
b) the crash on Windows is now fixed for 3.2, and 3.3
Hence I'm closing this issue as fixed.
--
resolution:
Terry J. Reedy tjre...@udel.edu added the comment:
64 bit win 7, 3.3.0a1 crashes also.
Idle shell just says that fd 0 is not valid, which I expect is correct for the
socket replacement for sys.stdout.
--
nosy: +terry.reedy
___
Python tracker
Changes by R. David Murray rdmur...@bitdance.com:
--
title: Python 3 interpreter crash on windows when stdin closed - Python 3
interpreter crash on windows when stdin closed in Python shell
___
Python tracker rep...@bugs.python.org
Alexis Daboville alexis.dabovi...@gmail.com added the comment:
@Amaury: ok thanks, I never heard of this argument before.
I tried to reproduce the crash in the Python shell embedded in IDLE and there's
no crash (same version 3.2.2, Windows 7): http://i.imgur.com/ayT96.png
--
Martin v. Löwis mar...@v.loewis.de added the comment:
The crash occurs in the my_fgets implementation, namely when the CRT performs
its (standards-violating) parameter validation. The attached patch works around
this CRT bug (as has been done in other places already).
--
keywords:
