Message6620

Author	alex
Recipients	alex
Date	2011-08-29.11:46:57
SpamBayes Score	0.0014853188
Marked as misclassified	No
Message-id	<1314618418.27.0.810377967352.issue1789@psf.upfronthosting.co.za>
In-reply-to

Content
It is by purpose, as written in the jython book. So it is not a bug. From http://www.jython.org/jythonbook/en/1.0/Concurrency.html A threading.Lock ensures entry by only one thread. (In Jython, but unlike CPython, such locks are always reentrant; there’s no distinction between threading.Lock and threading.RLock.) Other threads have to wait until that thread exits the lock. Such explicit locks are the simplest and perhaps most portable synchronization to perform.

It is by purpose, as written in the jython book. So it is not a bug.

From http://www.jython.org/jythonbook/en/1.0/Concurrency.html

A threading.Lock ensures entry by only one thread. (In Jython, but unlike CPython, such locks are always reentrant; there’s no distinction between threading.Lock and threading.RLock.) Other threads have to wait until that thread exits the lock. Such explicit locks are the simplest and perhaps most portable synchronization to perform.

History
Date	User	Action	Args
2011-08-29 11:46:58	alex	set	messageid: <1314618418.27.0.810377967352.issue1789@psf.upfronthosting.co.za>
2011-08-29 11:46:58	alex	set	recipients: + alex
2011-08-29 11:46:58	alex	link	issue1789 messages
2011-08-29 11:46:57	alex	create