getpeername() on stdin?

[Roy Smith]

I want to do getpeername() on stdin. I know I can do this by wrapping a socket object around stdin, with

s = socket.fromfd(sys.stdin.fileno(), family, type)

but that requires that I know what the family and type are. What I want to do is discover the family and type by looking at what getpeername() and/or getsockname() return. Can this be done with the standard library?

 

[Nobody]

I want to do getpeername() on stdin. I know I can do this by wrapping a
socket object around stdin, with

s = socket.fromfd(sys.stdin.fileno(), family, type)

but that requires that I know what the family and type are. What I want
to do is discover the family and type by looking at what getpeername()
and/or getsockname() return. Can this be done with the standard library?

I think that you'd need to use ctypes to access the underlying
getpeername() function from libc.

 

[random832]

I think that you'd need to use ctypes to access the underlying
getpeername() function from libc.

If it's possible to get this information with only the fd, then why does
socket.fromfd require them?

 

[Roy Smith]

If it's possible to get this information with only the fd, then why does
socket.fromfd require them?

Because socket.fromfd() is a very simplistic alternate way to create a
socket object, which meets a common use case that happens not to be my
use case.

 

[Nobody]

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.