Michael> I'm not familiar with the clever trick Greg is proposing, but I
Michael> do agree that _IF_ everything else were equal, then Queue seems
Michael> to belong in the threading module. My biggest reason is that I
Michael> think anyone who is new to threading probably shouldn't use any
Michael> communication mechanism OTHER than Queue or something similar
Michael> which has been carefully designed by someone knowlegable.
Is the Queue class very useful outside a multithreaded context? The notion
of a queue as a data structure has meaning outside of threaded applications.
Its presence might seduce a new programmer into thinking it is subtly
different than it really is. A cursory test suggests that it works, though
q.get() on a empty queue seems a bit counterproductive. Also, Queue objects
are probably quite a bit less efficient than lists. Taken as a whole,
perhaps a stronger attachment with the threading module isn't such a bad
idea.
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4