Message259374
You are right that get_nowait() is the correct api for my use case, using get_nowait() nothing is pushed to the internal _getters deque. The reason for my us of get() is that job futures are created one place in the code and then thrown in a processing function that will yield the job future. This design was created to handle all exceptions in processing(), but I agree that get_nowait would have been the superior solution.
I do not have time on my hands right now to take on the challenge of writing a patch, but I might take it up later, sound fun ;)
Good day to you sir, and thank you for the feedback. |
|
Date |
User |
Action |
Args |
2016-02-02 10:25:50 | Brunsgaard | set | recipients:
+ Brunsgaard, gvanrossum, vstinner, yselivanov |
2016-02-02 10:25:50 | Brunsgaard | set | messageid: <1454408750.3.0.262967898093.issue26259@psf.upfronthosting.co.za> |
2016-02-02 10:25:50 | Brunsgaard | link | issue26259 messages |
2016-02-02 10:25:49 | Brunsgaard | create | |
|