Message 273250 - 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	martin.panter
Recipients	christian.heimes, martin.panter
Date	2016-08-20.22:51:34
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1471733494.47.0.0649589440463.issue27816@psf.upfronthosting.co.za>
In-reply-to

Content
The documentation already says “Socket objects also have these (read-only) attributes that correspond to the values given to the socket constructor. . . . socket.proto”. For existing versions of Python, I’m not sure there is much else we can do. In Issue 27377, I mentioned the idea of using the logic there (SO_PROTOCOL etc) to determine the socket.proto attribute automatically.

The documentation already says “Socket objects also have these (read-only) attributes that correspond to the values given to the socket constructor. . . . socket.proto”. For existing versions of Python, I’m not sure there is much else we can do.

In Issue 27377, I mentioned the idea of using the logic there (SO_PROTOCOL etc) to determine the socket.proto attribute automatically.

History
Date	User	Action	Args
2016-08-20 22:51:34	martin.panter	set	recipients: + martin.panter, christian.heimes
2016-08-20 22:51:34	martin.panter	set	messageid: <1471733494.47.0.0649589440463.issue27816@psf.upfronthosting.co.za>
2016-08-20 22:51:34	martin.panter	link	issue27816 messages
2016-08-20 22:51:34	martin.panter	create