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 docs@python, martin.panter
Date 2016-06-29.02:54:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467168896.94.0.840314714269.issue27409@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation just says that SO_* etc constants are defined. However when people add new ones, they add them as new features to a specific version (not backported as bug fixes), but do not alter the documentation at all. IMO it is silly adding undocumented features. E.g. Issue 26907 was opened to add (among others) SO_PASSCRED, which was already added, undocumented, as part of Issue 6560.

This patch attempts to indicate which symbols are defined by Python (depending on OS availability), and therefore one can deduce if Python does not define a particular symbol. It could be adapted to the 2.7 documentation, but I am not really motivated for that on my own.

I also remove a redundant definition in the module, and removed a conditional because SO_REUSEADDR is required to always be defined according to the test suite. These specific changes should only be applied to 3.6.

I also found Issue 1732367, which has a patch documenting each AF_* symbol in a little more detail. That patch was never updated nor comitted, but it sounds like this kind of addition might be acceptable.
History
Date User Action Args
2016-06-29 02:54:56martin.pantersetrecipients: + martin.panter, docs@python
2016-06-29 02:54:56martin.pantersetmessageid: <1467168896.94.0.840314714269.issue27409@psf.upfronthosting.co.za>
2016-06-29 02:54:56martin.panterlinkissue27409 messages
2016-06-29 02:54:55martin.pantercreate