Message 196475 - 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	neologix
Recipients	neologix, pitrou, python-dev, sbt, vstinner
Date	2013-08-29.18:24:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAH_1eM1w3q9rHGdjUBzvdMyx02eNv=NzzN2Hqu0VaUjNkqdMoA@mail.gmail.com>
In-reply-to	<3cQrP131b1z7Ll3@mail.python.org>

Content
Alright, I chose a 16MB size for SOCK_MAX_SIZE because nowadays, one can encounter large buffers for Gigabit/10Gb Ethernet. Regarding the original issue: is it OK to add it as socket.socketpair(), or should it only be added to test.support? Since I don't use Windows, I don't know if this deserves being expose in socket module, but having socketpair() available in the test suite would be really useful (for example, most select tests aren't run on Windows because they use pipes).

Alright, I chose a 16MB size for SOCK_MAX_SIZE because nowadays, one
can encounter large buffers for Gigabit/10Gb Ethernet.

Regarding the original issue: is it OK to add it as
socket.socketpair(), or should it only be added to test.support?
Since I don't use Windows, I don't know if this deserves being expose
in socket module, but having socketpair() available in the test suite
would be really useful (for example, most select tests aren't run on
Windows because they use pipes).

History
Date	User	Action	Args
2013-08-29 18:24:15	neologix	set	recipients: + neologix, pitrou, vstinner, python-dev, sbt
2013-08-29 18:24:15	neologix	link	issue18643 messages
2013-08-29 18:24:15	neologix	create