* Michael Hudson: > Not to my knowledge. I've always thought that it would be pretty > hard. I'd be interested in being proved wrong. The real problem is that you can ditch most extension modules. 8-( It sounds more like a fun project for the Python core, though. >> Copying GC might help to get rid of the GIL *and* improve performance >> in the accept+fork model (because read-only object access does not >> trigger copy-on-write anymore). > > How does a copying gc differ much from a non-copying non-refcounted gc > here? You could copy immutable objects to a separate set of pages and never collect them (especially if recursively refer to immutable objects only).
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