In article <[EMAIL PROTECTED]>,
Alex <[EMAIL PROTECTED]> wrote:
>
>In order to understand the concept of threading pool in python I'm
>working on a simple single-site web crawler.
You can also compare your code against
http://www.pythoncraft.com/OSCON2001/ThreadPoolSpider.py
--
Aahz ([EMAIL PR
On May 17, 2:23 pm, Jeff <[EMAIL PROTECTED]> wrote:
> Your worker threads wait around forever because there is no place for
> them to exit. Queue.get() by default blocks until there is an item in
> the queue available. You can do something like this to cause the
> worker to quit when the queue is
Your worker threads wait around forever because there is no place for
them to exit. Queue.get() by default blocks until there is an item in
the queue available. You can do something like this to cause the
worker to quit when the queue is empty. Just make sure that you fill
the queue before start
Hi all.
In order to understand the concept of threading pool in python I'm
working on a simple single-site web crawler.
I would like to stop the program when the threading pool have
downloaded all internal links from a web site, but now my program keep
waiting forever even if there are no more lin
