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 neologix
Recipients docs@python, georg.brandl, kiilerix, neologix, nicdumz, pitrou
Date 2012-01-14.10:29:41
SpamBayes Score 1.5130428e-07
Marked as misclassified No
Message-id <CAH_1eM3xmAn_cNogpvDHZS2Zt5b13aE8utpo_5218dxt-P1sYw@mail.gmail.com>
In-reply-to <1326402982.11.0.0757175288221.issue6774@psf.upfronthosting.co.za>
Content
> This is questionable, unexpected, and should be documented.

There's already this note at the top of the socket module documentation:
"""
Note

Some behavior may be platform dependent, since calls are made to the
operating system socket APIs.
"""

There are other such subtleties with the socket API, e.g. SO_REUSEADDR
which doesn't have the same semantics on Windows. As I said earlier, I
don't think we should document every platform quirks: it will make
users worry for no reason, and as time passes, there's a chance that
the documentation doesn't match the actual behavior.
For example, this specific behavior might very well be a bug, and it's
not our responsibility to document this.
History
Date User Action Args
2012-01-14 10:29:42neologixsetrecipients: + neologix, georg.brandl, pitrou, kiilerix, nicdumz, docs@python
2012-01-14 10:29:42neologixlinkissue6774 messages
2012-01-14 10:29:41neologixcreate