Message220280
| Author |
vajrasky |
| Recipients |
gvanrossum, vajrasky, vstinner, yselivanov |
| Date |
2014-06-11.15:59:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1402502394.97.0.183524227653.issue21723@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
import asyncio
loop = asyncio.get_event_loop()
q = asyncio.Queue(maxsize=1.2, loop=loop)
q.put_nowait(1)
q.put_nowait(1)
q.put_nowait(1)
q.put_nowait(1)
q.put_nowait(1)
.... and so on
It seems counter intuitive for my innocent eyes. As comparison with the traditional queue:
import queue
q = queue.Queue(maxsize=1.2)
q.put(1)
q.put(1)
q.put(1) -> blocking
Here is the patch to make the behaviour consistent with its sibling. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014-06-11 15:59:55 | vajrasky | set | recipients:
+ vajrasky, gvanrossum, vstinner, yselivanov |
| 2014-06-11 15:59:54 | vajrasky | set | messageid: <1402502394.97.0.183524227653.issue21723@psf.upfronthosting.co.za> |
| 2014-06-11 15:59:54 | vajrasky | link | issue21723 messages |
| 2014-06-11 15:59:54 | vajrasky | create | |
|