Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #7473 > unrolled thread

Re: which threading libraries to use?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: which threading libraries to use? Chris Angelico <rosuav@gmail.com> - 2011-06-12 15:01 +1000

#7473 — Re: which threading libraries to use?

On Sun, Jun 12, 2011 at 2:10 PM, Dennis <daodennis@gmail.com> wrote:
> Hi,
>
> Are there any reasons besides personal preference to use one
> particular threading library over the other?  Eventlet, Twisted, and
> Python's native Threading class, or are there even others?  Are there
> any licensing or redistribution restrictions that I should be worried
> about?  Which ones do you consider best documented?  Most thread-safe?
> Efficient?

I use the native Threading class, myself, largely because it's so easy
to switch to multiprocessing if the GIL starts to get in the way. YMMV
if you don't use CPython.

> Ultimately this will be used for asynchronous SNMP, HTTP, and WMI.  I
> don't think this will need to evolve into a multi-process project,
> unless of course that is much easier to do than multi-threading?

In all probability, your threads will spend 99% of their time waiting
for the network. This makes threads very effective, and largely
eliminates the GIL issues (if they occasionally have to take turns,
it's not going to affect things much). Pick whichever threading
library suits your coding style; they'll all work, most likely.

Chris Angelico

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web