[Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-09 Thread Robert
Talin wrote: / I don't know how you define simple. In order to be able to have // separate GILs you have to remove *all* sharing of objects between // interpreters. And all other data structures, too. It would probably // kill performance too, because currently obmalloc relies on the GIL. /

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-06 Thread Josiah Carlson
Talin [EMAIL PROTECTED] wrote: Guido van Rossum wrote: I don't know how you define simple. In order to be able to have separate GILs you have to remove *all* sharing of objects between interpreters. And all other data structures, too. It would probably kill performance too, because

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-05 Thread James Y Knight
On Nov 4, 2006, at 3:49 AM, Martin v. Löwis wrote: Notice that at least the following objects are shared between interpreters, as they are singletons: - None, True, False, (), , u - strings of length 1, Unicode strings of length 1 with ord 256 - integers between -5 and 256 How do you deal

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-05 Thread Guido van Rossum
On 11/5/06, James Y Knight [EMAIL PROTECTED] wrote: On Nov 4, 2006, at 3:49 AM, Martin v. Löwis wrote: Notice that at least the following objects are shared between interpreters, as they are singletons: - None, True, False, (), , u - strings of length 1, Unicode strings of length 1 with

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-05 Thread Talin
Guido van Rossum wrote: I don't know how you define simple. In order to be able to have separate GILs you have to remove *all* sharing of objects between interpreters. And all other data structures, too. It would probably kill performance too, because currently obmalloc relies on the GIL.

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-04 Thread Martin v. Löwis
Robert schrieb: Would it be a possibilty in next Python to have the lock separate for each Interpreter instance. Thus: have *interpreter_lock separate in each PyThreadState instance and only threads of same Interpreter have same GIL? Separation between Interpreters seems to be enough. The

[Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-03 Thread Robert
repeated from c.l.p : Feature Request: Py_NewInterpreter to create separate GIL (branch) Daniel Dittmar wrote: robert wrote: I'd like to use multiple CPU cores for selected time consuming Python computations (incl. numpy/scipy) in a frictionless manner. Interprocess communication is

Re: [Python-Dev] Feature Request: Py_NewInterpreter to create separate GIL (branch)

2006-11-03 Thread Brett Cannon
On 11/3/06, Robert [EMAIL PROTECTED] wrote: repeated from c.l.p : Feature Request: Py_NewInterpreter to createseparate GIL (branch)Daniel Dittmar wrote: robert wrote: I'd like to use multiple CPU cores for selected time consuming Python computations (incl. numpy/scipy) in a frictionless