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 gvanrossum
Recipients gvanrossum, thehesiod, vstinner, yselivanov
Date 2015-11-11.21:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKFRc9pM+Pb48OkkakTypMtMtCyrwDy6sjAUy=wOCX+ZQ@mail.gmail.com>
In-reply-to <1447263015.93.0.232616636818.issue25593@psf.upfronthosting.co.za>
Content
Sorry, the code you posted is still incomprehensible. E.g. I suppose your
worker doesn't really have
```
obj = self.queue.get()
```
but rather something like
```
obj = yield from async_queue.get()
```
But in the end, even with that hypothesis, I can't explain what you're
seeing, and I believe there is a bug related to bad mixing multiprocessing
and asyncio in some code you're not showing, and your "fix" just masks the
problem. Note that the code you posted doesn't touch sockets in any way,
while the issue you're seeing is related to sockets. So there *must* be
more to it.
History
Date User Action Args
2015-11-11 21:33:51gvanrossumsetrecipients: + gvanrossum, vstinner, yselivanov, thehesiod
2015-11-11 21:33:51gvanrossumlinkissue25593 messages
2015-11-11 21:33:51gvanrossumcreate