Talin <talin at acm.org> 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 currently obmalloc relies on the GIL. > > Nitpick: You have to remove all sharing of *mutable* objects. One day, > when we get "pure" GC with no refcounting, that will be a meaningful > distinction. :) Python already grew that feature a couple years back, but it never became mainline. Search google (I don't know the magic incantation off the top of my head), buf if I remember correctly, it wasn't a significant win if any at all. - Josiah
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4