> Pypi has what, 500k projects on it? Many abandoned. > Whom exactly is going to update those? > once all the hard work is done by the community. If I want t

> Pypi has what, 500k projects on it? Many abandoned. > Whom exactly is going to update those? > once all the hard work is done by the community. If I want to use Python with parallel threads in the app I'm building, I don't need to wait for every last one of those 500k packages. I can wait for only the packages I'm using, or risk it and force Python to run in nogil mode anyway. It's my choice. > Or do packages get an automatic “doesn’t work with no-GIL” unless the author explicitly opts to enable it? As other comments say in this thread: yes. > Does that remind you of anything? > Mmm. 2-to-3 burned you. We get it. You might be getting flashbacks to that nightmare. That is understandable. But you need to look beyond a surface level similarity — "That was a transition. This is a transition. They're identical!" — and at the actual transition itself. The problems of 2-to-3 aren't present here. The user is not forced to choose between two incompatible options. Library authors aren't forced to migrate their code forward. Users and library authors do not need to collectively choose one version over another. The newer version remains compatible with older code. The sky is not falling.