Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #74162
| References | <mailman.11616.1404796682.18130.python-list@python.org> <53bbb33b$0$2926$c3e8da3$76491128@news.astraweb.com> |
|---|---|
| Date | 2014-07-08 20:35 +1000 |
| Subject | Re: error handling when opening files |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.11622.1404815761.18130.python-list@python.org> (permalink) |
On Tue, Jul 8, 2014 at 7:00 PM, Steven D'Aprano <steve@pearwood.info> wrote: > Interestingly, did you know that even *closing* a file can fail? I know that can happen with SSL sockets (which can require writing and reading). Can't think of any situations on normal file systems where that's true, unless the actual failure is in the flushing of buffers; technically, that's not a failure of closing, but it could be a failure that's detected on close(). Is that what you're thinking of? ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
error handling when opening files Alex Burke <alexjeffburke@gmail.com> - 2014-07-08 01:49 +0200
Re: error handling when opening files Marko Rauhamaa <marko@pacujo.net> - 2014-07-08 11:30 +0300
Re: error handling when opening files Steven D'Aprano <steve@pearwood.info> - 2014-07-08 09:00 +0000
Re: error handling when opening files Chris Angelico <rosuav@gmail.com> - 2014-07-08 20:35 +1000
Re: error handling when opening files Alex Burke <alexjeffburke@gmail.com> - 2014-07-09 21:59 +0200
Re: error handling when opening files wxjmfauth@gmail.com - 2014-07-08 02:38 -0700
csiph-web