[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: docs@python -> ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> enhancement ___ Python tracker

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Roundup Robot added the comment: New changeset 1e5e7064e872 by Ezio Melotti in branch '2.7': #1: document default values for socket.getaddrinfo in the text to clarify that it doesn't accept keyword args. http://hg.python.org/cpython/rev/1e5e7064e872 -- nosy: +python-dev ___

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Ezio Melotti added the comment: In that case I think it's OK to use the [] and mention the default values in the text. -- ___ Python tracker ___

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Chris Jerdonek added the comment: This issue only applies to 2.7. Keyword arguments are accepted in 3.x. See the interactive example here, for example: http://docs.python.org/3.2/library/socket.html#socket.getaddrinfo -- versions: -Python 2.6 ___

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Ezio Melotti added the comment: > Personally, I think explicitly stating in the text that the parameters > are positional-only can't hurt, especially since that's the rarer case, > no? OTOH it's an implementation detail that might be changed at some point. The other option is to use [] in the si

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Chris Jerdonek added the comment: Is issue 13386 one of the issues you had in mind, Éric? I don't know the current best practices for all of the signature edge cases, but Ezio might. Personally, I think explicitly stating in the text that the parameters are positional-only can't hurt, especia

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Éric Araujo added the comment: There are two or three issues on this tracker where we discuss the parameters notation conventions. I think I remember a proposal to add text explaining that the keyword notation does not imply that the function accepts keyword argument, only that there is a def

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

Chris Jerdonek added the comment: This might be a good place to use the newly-documented "positional-only" nomenclature: http://docs.python.org/2.7/glossary.html#term-parameter -- nosy: +chris.jerdonek ___ Python tracker

[issue16666] docs wrongly imply socket.getaddrinfo takes keyword arguments in 2.x

New submission from Mikel Ward: The docs for 2.6 and 2.7 say socket.getaddrinfo takes keyword arguments. http://docs.python.org/release/2.6.6/library/socket.html?highlight=socket#socket.getaddrinfo > socket.getaddrinfo(host, port, family=0, socktype=0, proto=0, flags=0) But that doesn't actual