3 ms·
apparently they did
by arthurcolle 5y ago
apparently they did
- reikonomusha 5y agoGetting rid of the GIL isn’t the hard part. It’s getting rid of the GIL and having existing Python code continue to work, with C extensions and all.
- thomasjudge 5y agoWhere is this documented
- rafaelgarrido 5y agoThere's some info on the proposal here: https://news.ycombinator.com/item?id=28896367 https://news.ycombinator.com/item?id=28896367
- quietbritishjim 5y agoI think the root comment is asking whether this new Python-on-Rust interpreter for rid of the GIL. Your link is about the existing CPython interpreter.
- grawp 5y agoWhy document something they have not implemented?
- michaelmior 5y agoBecause rightly or wrongly, tons of existing Python code implicitly requires on the GIL to function correctly. Especially when you have C extensions that may not be thread-safe.