- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message232113
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 | arigo |
|---|---|
| Recipients | arigo, neologix, nikratio, pitrou, serhiy.storchaka, vstinner |
| Date | 2014-12-04.09:57:57 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1417687077.51.0.906127139455.issue17852@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I hate to repeat myself, but if the C standard says "files are flushed at exit"; if Python 2 follows this standard; and if Python 3 follows it most of the time but *not always*... then it seems to me that something is very, very buggy in the worst possible way (rare data loss). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-12-04 09:57:57 | arigo | set | recipients: + arigo, pitrou, vstinner, nikratio, neologix, serhiy.storchaka |
| 2014-12-04 09:57:57 | arigo | set | messageid: <1417687077.51.0.906127139455.issue17852@psf.upfronthosting.co.za> |
| 2014-12-04 09:57:57 | arigo | link | issue17852 messages |
| 2014-12-04 09:57:57 | arigo | create | |

