> My original report was for 32 bit debug build on 64 bit Win 7 machine.
> I just re-ran test_multiprocessing with installed 64 bit python with same 
> result. Was "I don't see these errors." on different Windows or non-Windows.

On 64-bit Windows 7 with both 32 and 64 bit builds.

> One option is to skip the failing sub-tests on Windows, like some other sub-tests:
> skipped 'does not work with windows sockets'
> and consider the limitation on use of multi-processing in 2.7,3.2 as "won't fix". 
> (My view is that 3.2 users should upgrade as soon as dependencies allow.) 

Yes, I would be inclined to do that.

> Backporting new features requires pydev discussion.

I only meant exposing that functionality in the private _multiprocessing extension.