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 sbt
Recipients giampaolo.rodola, kristjan.jonsson, sbt
Date 2012-03-19.21:42:08
SpamBayes Score 0.0051543256
Marked as misclassified No
Message-id <1332193328.81.0.864408874389.issue14310@psf.upfronthosting.co.za>
In-reply-to
Content
> If duplication happened early, then there would have to be a way to 
> "unduplicate" it in the source process if, say, IPC somehow failed.  
> There is currently no api to undo the effects of WSADuplicateSocket().

If this were a normal handle then you could use the DUPLICATE_CLOSE_SOURCE flag with DuplicateHandle() to close it.  But using DuplicateHandle() with socket handles is discouraged.

I find the ability to duplicate and close handles in unrelated processes of the same user rather surprising.
History
Date User Action Args
2012-03-19 21:42:08sbtsetrecipients: + sbt, kristjan.jonsson, giampaolo.rodola
2012-03-19 21:42:08sbtsetmessageid: <1332193328.81.0.864408874389.issue14310@psf.upfronthosting.co.za>
2012-03-19 21:42:08sbtlinkissue14310 messages
2012-03-19 21:42:08sbtcreate