3 ms·
Except they're not at all analogous situations. In python 2 -> 3, if a new version of a library came out Python 3 only, you couldn't use both it, and your old P
by ctoth 3y ago
Except they're not at all analogous situations.
In python 2 -> 3, if a new version of a library came out Python 3 only, you couldn't use both it, and your old Python 2 code at the same time.
Here, you can use the GIL until every one of your dependencies have migrated, even as new versions of your dependencies come out with nogil support until one magical day they all have nogil and you can migrate. But since you have been able to keep up with the library and weren't just arbitrarily cut off at their last Python2/GIL version, it's not a huge breaking change!
- miraculixx 3y ago* removed comment as it was factually false *
- usrbinbash 3y ago> If it was like you say there would be no need for the --nogil cli option. Testing the difference between running it with and without `nogil` without having to install 2 different interpreters. Testing libraries during transitions. Simply giving users a choice. Convenience. Almost no one uses pre-Go.1.11 (GOPATH instead of Modules) any more for project organisation, and the transition is trivially easy. And yet, the toolchain still reacts to `GO111MODULE=off`.