We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queue
It's a little awkward calling ezq.put_msg and ezq.iter_msg. I think I'd prefer:
ezq.put_msg
ezq.iter_msg
q = ezq.Q() # simple constructor q.put(data, kind='special', order=1) # constructs the message for msg in q: # simple iteration # something with msg.data q.end()
The text was updated successfully, but these errors were encountered:
A quick test suggests this is kinda nice. Maybe I like this better than the functions.
Sorry, something went wrong.
Why not both? Because idioms matter and the examples will be what people remember.
Ok, but why not both, under-the-hood. Like keep the functions as the primitive operations, but include the wrappers for convenience.
Maybe. Will probably keep both for a little bit to see what it's like.
Of course now the functions for creating the workers and ending them feel weird.
run
run_thread
b631c1a
No branches or pull requests
It's a little awkward calling
ezq.put_msg
andezq.iter_msg
. I think I'd prefer:The text was updated successfully, but these errors were encountered: