By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,100 Members | 2,979 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,100 IT Pros & Developers. It's quick & easy.

global interpreter lock

P: n/a
I just need confirmation that I think right.

Is the files thread_xxx.h (xxx = nt, os2 or whatever) responsible for
the
global interpreter lock in a multithreaded environment?

I'm currently writing my own thread_VW for VxWorks, thats why I'm
asking.

//Tommy

Oct 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
To**********@gmail.com wrote:
I just need confirmation that I think right.

Is the files thread_xxx.h (xxx = nt, os2 or whatever) responsible for
the
global interpreter lock in a multithreaded environment?

I'm currently writing my own thread_VW for VxWorks, thats why I'm
asking.

//Tommy

Someone can correct me if I'm wrong, but the lock actually lives in
ceval.c, around here:

802 PyThread_release_lock(interpreter_lock);
803
804 /* Other threads may run now */
805
806 PyThread_acquire_lock(interpreter_lock, 1);
This was taken from what appears to be a 2.4.1 release rather than a CVS
checkout. It looks like the PyThread_type_lock is defined in the
thread_xxx.h files, though.

HTH,

- jmj
Oct 18 '05 #2

P: n/a
Thanks,
PyThread_release_lock() is implemented in all thread_xxx.h files.

So I thought right but specified my question like a stupid ;)

//T

Oct 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.