Hacker News Reader

> concurrency-related bugs that have been masked by the GIL

Yeah... could phrase this as "All programs written with the assumption of a GIL are now broken" instead. Wish they had done this as part of the breaking changes for python 3, I guess they'll have to wait for Python 4 for this?

View on HN

GIL can remain default on. Users can simply disable it for chosen parts of their program.

No they can’t, it would have to be disabled or enabled globally at the process and/or interpreter level.

I think I read that there won’t be another big jump like there was for Python 2-3. If I understood correctly, there could be a Python 4, but it won’t indicate huge breaking changes, it’ll just be another release

Reply on news.ycombinator.com