Threading modeule and condition??

[Ishwar Rattan]

System is Mandrake-9.1 with Python-2.3.4

I need to learn condition variables (mentioned in Section 7.5.3 of library
reference) but I am confused on the way of creating one. The documentation
says:
---
# Produce one item
cv.acquire()
make_an_item_av ailable()
cv.notify()
cv.release()

To choose between notify() and notifyAll(), consider whether one state
change can be interesting for only one or several waiting threads. E.g. in
a typical producer-consumer situation, adding one item to the buffer only
needs to wake up one consumer thread.

class Condition([lock])

If the lock argument is given and not None, it must be a Lock or RLock
object, and it is used as the underlying lock. Otherwise, a new RLock object
is created and used as the underlying lock.
---

how do I insttantiate 'cv' the condition object in the first place. A code
fragment will be helpful.

-ishwar

[Christopher T King]

On 23 Jul 2004, Ishwar Rattan wrote:

how do I insttantiate 'cv' the condition object in the first place. A code
fragment will be helpful.

from threading import Condition cv = Condition()

Just like any object ;)

Just make sure you do this _before_ creating your threads, so that the
object is shared by all the threads when they are created.

[David Bolen]

Christopher T King <sq******@WPI.E DU> writes:

Just make sure you do this _before_ creating your threads, so that the
object is shared by all the threads when they are created.

Order of creation shouldn't make any difference. Condition objects
(as all of the synchronization objects built on top of the lock
primitive) exist independent of thread's per-se. They are designed
for use from multiple-threads, so it doesn't matter if they are
created before or after the threads that use them, although obviously
you need to hand the threads references to the objects they are going
to use.

-- David

[Christopher T King]

On 23 Jul 2004, David Bolen wrote:

Christopher T King <sq******@WPI.E DU> writes:

Just make sure you do this _before_ creating your threads, so that the
object is shared by all the threads when they are created.

Order of creation shouldn't make any difference. Condition objects
(as all of the synchronization objects built on top of the lock
primitive) exist independent of thread's per-se. They are designed
for use from multiple-threads, so it doesn't matter if they are
created before or after the threads that use them, although obviously
you need to hand the threads references to the objects they are going
to use.

That's more what I was getting at, "make sure you create one and pass it
to all your threads instead of creating different ones in each thread".
Poor wording on my part.

[Aahz]

In article <93************ **************@ posting.google. com>,
Ishwar Rattan <ra****@cps.cmi ch.edu> wrote:

I need to learn condition variables (mentioned in Section 7.5.3 of library
reference) but I am confused on the way of creating one.

Right. That's why you don't use conditions. Use Queue.Queue instead.
--
Aahz (aa**@pythoncra ft.com) <*> http://www.pythoncraft.com/

"To me vi is Zen. To use vi is to practice zen. Every command is a
koan. Profound to the user, unintelligible to the uninitiated. You
discover truth everytime you use it." --*****@lion.aust in.ibm.com