Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #95843
| From | Laura Creighton <lac@openend.se> |
|---|---|
| Subject | Re: Low level file descriptors and high-level Python files |
| References | <55e5bcd3$0$1639$c3e8da3$5496439d@news.astraweb.com> |
| Date | 2015-09-01 19:41 +0200 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.53.1441129318.23514.python-list@python.org> (permalink) |
In a message of Wed, 02 Sep 2015 00:57:22 +1000, "Steven D'Aprano" writes: >Let's suppose somebody passes me a file descriptor to work with. It could >come from somewhere else, but for the sake of discussion let's pretend I >create it myself this way: >Q1: In this example, I know that I opened the fd in write mode, because I >did it myself. But since I'm not actually opening it, how do I know what >mode to use in the call to fdopen? Is there something I can call to find >out what mode a file descriptor has been opened with? for POSIX things use fnclt. YOu have to parese the bits yourself and I always have to look that up to see what the grubby details are. No clue what you do on windows. Don't go around closing things you don't know are open. They could be some other processes' thing. Laura
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Low level file descriptors and high-level Python files Steven D'Aprano <steve@pearwood.info> - 2015-09-02 00:57 +1000
Re: Low level file descriptors and high-level Python files random832@fastmail.us - 2015-09-01 11:56 -0400
Re: Low level file descriptors and high-level Python files Laura Creighton <lac@openend.se> - 2015-09-01 19:41 +0200
Re: Low level file descriptors and high-level Python files Grant Edwards <invalid@invalid.invalid> - 2015-09-01 22:19 +0000
Re: Low level file descriptors and high-level Python files Laura Creighton <lac@openend.se> - 2015-09-02 09:02 +0200
csiph-web