Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #58359
| From | Nobody <nobody@nowhere.com> |
|---|---|
| Subject | Re: getpeername() on stdin? |
| Date | 2013-11-03 03:27 +0000 |
| Message-Id | <pan.2013.11.03.03.27.20.540000@nowhere.com> |
| Newsgroups | comp.lang.python |
| References | <mailman.1885.1383236191.18130.python-list@python.org> <pan.2013.11.01.01.12.30.485000@nowhere.com> <mailman.1937.1383332149.18130.python-list@python.org> |
| Organization | Zen Internet |
On Fri, 01 Nov 2013 14:55:38 -0400, random832 wrote: > If it's possible to get this information with only the fd, then why does > socket.fromfd require them? The only person who can answer that is whoever came up with socket.fromfd() in the first place. I initially suspected that it might have been a Windows limitation, but socket.fromfd() is only available on Unix.
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
getpeername() on stdin? Roy Smith <roy@panix.com> - 2013-10-31 12:16 -0400
Re: getpeername() on stdin? Nobody <nobody@nowhere.com> - 2013-11-01 01:12 +0000
Re: getpeername() on stdin? random832@fastmail.us - 2013-11-01 14:55 -0400
Re: getpeername() on stdin? Roy Smith <roy@panix.com> - 2013-11-01 20:26 -0400
Re: getpeername() on stdin? Nobody <nobody@nowhere.com> - 2013-11-03 03:27 +0000
csiph-web