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 neologix
Recipients arigo, neologix, pitrou, vstinner
Date 2013-04-29.17:13:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1xWKxM0xnaWqqzgnXcToQHSpBboi7Y7XiUn=Pa0xetbQ@mail.gmail.com>
In-reply-to <1367253979.55.0.888489202089.issue17852@psf.upfronthosting.co.za>
Content
> "When you say Python 2, I assume you mean CPython 2, right?
> Because - AFAICT - files got flushed only by accident, not by design."
>
> It looks to be a feature of the standard C library, at least the GNU libc. Its libio library installs an exit handler flushing all open files. You can see it if you set a breaking on write() using gdb:

Yes, it's guaranteed by POSIX/ANSI (see man exit).
I was refering to the fact that the automatic flushing of files upon
exit is a mere side effect of the implementation based atop stdio
stream in cpython 2. It's no guaranteed by any Python spec (and I
can't really think of any platform other than C that makes such
guarantee).
History
Date User Action Args
2013-04-29 17:13:52neologixsetrecipients: + neologix, arigo, pitrou, vstinner
2013-04-29 17:13:52neologixlinkissue17852 messages
2013-04-29 17:13:52neologixcreate