Message188137
| Author |
vstinner |
| Recipients |
arigo, neologix, pitrou, vstinner |
| Date |
2013年04月30日.07:54:49 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAMpsgwaWF3xawNGRSD7oZ==naHe92kVh7a9oTU6V4GE_-rsY3Q@mail.gmail.com> |
| In-reply-to |
<CAH_1eM3CX3D8ddk7iaaVA-Q0tT7RVc9Rrib7xQR0FdZon66vjw@mail.gmail.com> |
| Content |
> It's guaranteed for exit(), not _Exit()/_exit().
Oops ok, thanks.
2013年4月30日 Charles-François Natali <report@bugs.python.org>:
>
> Charles-François Natali added the comment:
>
>> Hum, POSIX (2004) is not so strict:
>> "Whether open streams are flushed or closed, or temporary files are
>> removed is implementation-defined."
>> http://pubs.opengroup.org/onlinepubs/009695399/functions/exit.html
>
> You're looking at the wrong section:
>
> "The exit() function shall then flush all open streams with unwritten
> buffered data, close all open streams"
>
> Then a couple lines below:
>
> "The _Exit() [CX] and _exit() functions shall not call functions
> registered with atexit() nor any registered signal handlers. Whether
> open streams are flushed or closed, or temporary files are removed is
> implementation-defined."
>
> It's guaranteed for exit(), not _Exit()/_exit().
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue17852>
> _______________________________________ |
|