[Python-bugs-list] [ python-Feature Requests-793802 ] class for function calls that are not thread safe

[SourceForge.net]

Feature Requests item #793802, was opened at 2003-08-23 18:02
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=793802&group_id=5470

Category: Threads
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Elfring (elfring)
Assigned to: Nobody/Anonymous (nobody)
Summary: class for function calls that are not thread safe

Initial Comment:
I would like that a class will be added to perform thread unsafe 
function or method calls in an easy way like I describe it in the 
request 
"https://sourceforge.net/mailarchive/forum.php?thread_id=1585197&forum_id=24972" 
for the TCL thread package.
The description 
"http://zthread.sourceforge.net/html/classZThread_1_1SynchronousExecutor.html" 
seems to come near what I want. But I think that there is a little bit 
missing.

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2003-10-20 23:07

Message:
Logged In: YES 
user_id=21627

That feature is already available. You can easily provide a
module-global mutex that is used to protect all entry points
of some library. See _tkinter for one example, and
socketmodule.c for another.

----------------------------------------------------------------------

Comment By: Markus Elfring (elfring)
Date: 2003-09-07 15:02

Message:
Logged In: YES 
user_id=572001

I am looking for a monitor implementation that has got the scope of a 
library or package and not a single synchronized method or block like it 
is in Java.
A function object will get this monitor as a parameter.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=793802&group_id=5470