This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients
Date 2006-01-02.00:24:00
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31435

There's nothing Python can do about this short of
implementing I/O itself.  That isn't likely.  If someone is
truly bothered by this behavior on Windows (or any other
platform), they need to convince Microsoft (or other
relevant C vendors) to change _their_ stdio implementation
-- Python inherits the platform C's behavior, quirks and all.

I'll note that I'm not bothered by it.  It's one of those
"doctor, doctor, it hurts when I do this!" kinds of
pseudo-problems, IMO:  so don't do that.  It's not like
hostile user input can "trick" a Python application into
doing I/O operations in an undefined order.
History
Date User Action Args
2007-08-23 14:37:03adminlinkissue1394612 messages
2007-08-23 14:37:03admincreate