Message 225659 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Alexander.Patrakov
Recipients	Alexander.Patrakov, docs@python
Date	2014-08-22.11:43:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1408707808.63.0.0809888327352.issue22249@psf.upfronthosting.co.za>
In-reply-to

Content
See the example at https://docs.python.org/2/library/socket.html#socket.getaddrinfo >>> socket.getaddrinfo("www.python.org", 80, 0, 0, socket.SOL_TCP) As I am primarily a C programmer, it is quite surprising for me to see a SOL_* being passed into the proto argument. I thought that SOL_* is only for setsockopt(), and IPPROTO_* would be suitable. Yes, for TCP and UDP the SOL_* and IPPROTO_* constants are the same, but see e.g. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737530%28v=vs.85%29.aspx which specifically points out that IPPROTO_* constants as acceptable values.

See the example at https://docs.python.org/2/library/socket.html#socket.getaddrinfo

>>> socket.getaddrinfo("www.python.org", 80, 0, 0, socket.SOL_TCP)

As I am primarily a C programmer, it is quite surprising for me to see a SOL_* being passed into the proto argument. I thought that SOL_* is only for setsockopt(), and IPPROTO_* would be suitable. Yes, for TCP and UDP the SOL_* and IPPROTO_* constants are the same, but see e.g. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737530%28v=vs.85%29.aspx which specifically points out that IPPROTO_* constants as acceptable values.

History
Date	User	Action	Args
2014-08-22 11:43:28	Alexander.Patrakov	set	recipients: + Alexander.Patrakov, docs@python
2014-08-22 11:43:28	Alexander.Patrakov	set	messageid: <1408707808.63.0.0809888327352.issue22249@psf.upfronthosting.co.za>
2014-08-22 11:43:28	Alexander.Patrakov	link	issue22249 messages
2014-08-22 11:43:27	Alexander.Patrakov	create