Message159297
| Author |
pitrou |
| Recipients |
neologix, pitrou, sbt, vstinner |
| Date |
2012年04月25日.15:16:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1335367014.75.0.69258586538.issue14666@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I don't think that you should call pthread_sigmask(). It looks like a
> workaround for this issue, whereas resource_sharer.stop() is the
> correct fix.
The problem is not only with test_multiprocessing and test_socket; any test which uses multiprocessing could have side effects on any subsequent tests which uses signals. Also, applicative code could be affected.
So I think pthread_sigmask() *is* the solution. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年04月25日 15:16:54 | pitrou | set | recipients:
+ pitrou, vstinner, neologix, sbt |
| 2012年04月25日 15:16:54 | pitrou | set | messageid: <1335367014.75.0.69258586538.issue14666@psf.upfronthosting.co.za> |
| 2012年04月25日 15:16:54 | pitrou | link | issue14666 messages |
| 2012年04月25日 15:16:54 | pitrou | create |
|