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, vstinner
Date 2011-09-18.11:05:54
SpamBayes Score 3.21945e-05
Marked as misclassified No
Message-id <CAH_1eM3kFhT_PsXAj8g6GO=nWm2EoqmwHSxNits8qBKFB=i1wA@mail.gmail.com>
In-reply-to <1316340053.82.0.0896743748417.issue12981@psf.upfronthosting.co.za>
Content
> "It works fine on Linux, FreeBSD, OS X and Windows, but not on Solaris: see issue #12999."
>
> Oh, thank for testing before committing :) It's hard to debug multiprocessing.

Yes. Especially when you stumble upon a kernel/libc bug 25% of the time...

So, what should I do?
Apply the test catching the multiprocessing.connection ImportError to
test_multiprocessing (which is necessary even with the current C
version)?

And then apply the pure Python version, or wait until the OpenIndiana
case gets fixed?
History
Date User Action Args
2011-09-18 11:05:55neologixsetrecipients: + neologix, vstinner
2011-09-18 11:05:54neologixlinkissue12981 messages
2011-09-18 11:05:54neologixcreate