Author pitrou
Recipients christian.heimes, felipecruz, giampaolo.rodola, gvanrossum, meador.inge, neologix, pitrou, rosslagerwall, sbt, vstinner
Date 2013-08-24.20:45:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377377102.2475.10.camel@fsol>
In-reply-to <CAH_1eM3jBxdF7EP9Jp+k0TZSR0SjvG_NmgeTfixA2rEWUSr55g@mail.gmail.com>
Content
> > Didn't you forget to upload it?
> 
> I wanted to have answer to my questions first :-):

Ah, indeed, sorry!

> 1) In the documentation, I don't know how to best refer to files
> object registered: is "file descriptor" OK, or is it too low-level?
> Otherwise I'd be tempted to use just "file", but then this doesn't
> include sockets, pipes, etc. Or maybe "file object"/"file-like
> object"?

"file object" and "file-like object" are the convention used in the
docs:
http://docs.python.org/dev/glossary.html#term-file-object

That said, if the APIs also accept file descriptors, it must be
mentioned.

> i.e. have to unpack it for no reason.

That doesn't seem much of a concern, does it?
Perhaps there can be two separate methods, select() and
select_with_data(), but that sounds a bit overkill.

> 3) Concerning get_info(): right now the signature is:
> get_info(): fileobj -> (events, data)
> 
> Wouldn't it be better to just return the whole key instead [...]

No opinion :-)
History
Date User Action Args
2013-08-24 20:45:13pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, christian.heimes, meador.inge, neologix, rosslagerwall, sbt, felipecruz
2013-08-24 20:45:12pitroulinkissue16853 messages
2013-08-24 20:45:12pitroucreate