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 stutzbach
Recipients amaury.forgeotdarc, brian.curtin, christian.heimes, roudkerk, stutzbach, tim.golden
Date 2010-09-03.11:25:23
SpamBayes Score 0.00054211647
Marked as misclassified No
Message-id <1283513124.86.0.726815535299.issue9753@psf.upfronthosting.co.za>
In-reply-to
Content
On Windows, socket.dup is implemented using DuplicateHandle.  The documentation for DuplicateHandle reads:

You should not use DuplicateHandle to duplicate handles to the following objects:

    * I/O completion ports. No error is returned, but the duplicate handle cannot be used.
    * Sockets. No error is returned, but the duplicate handle may not be recognized by Winsock at the target process. Also, using DuplicateHandle interferes with internal reference counting on the underlying object. To duplicate a socket handle, use the WSADuplicateSocket function.
History
Date User Action Args
2010-09-03 11:25:25stutzbachsetrecipients: + stutzbach, amaury.forgeotdarc, christian.heimes, tim.golden, roudkerk, brian.curtin
2010-09-03 11:25:24stutzbachsetmessageid: <1283513124.86.0.726815535299.issue9753@psf.upfronthosting.co.za>
2010-09-03 11:25:23stutzbachlinkissue9753 messages
2010-09-03 11:25:23stutzbachcreate