Jython, GILs and object locking.

[Harri Pesonen]

Michael Chermside wrote:

> Luis P Caamano writes:
> 
>>I have no problem with the statement that removing the GIL
>>is hard and we don't have the resources to do that now.  I
>>understand that.  The statement I don't like is when people
>>say that "the GIL is not a problem at all and therefore,
>>it doesn't need fixing."
> 
> I don't think that people ARE saying that. I think that if
> you polled, most of the python developers would say that
> the GIL is an unfortunate limitation, but one which is
> particularly difficult to remove, since so MUCH of the
> Python interpreter is written with the assumption that
> the GIL is used.

I will remove GIL from Python. I have a Python script that takes the 
latest Python C API source code and makes necessary modifications. 
Currently it only handles some static objects, but eventually we have a 
GIL free Python (I call it Viper). I don't think that removing GIL is 
hard, on the contrary. The job is trivial but tedious.

Harri