No, for C/C++ you don't have to do anything unless the compiler writers add yet another new warning to -Wall -W, which you have to disable because it is spurious.
Java is more backwards compatible, so is Common Lisp.
Someone here said that the thread on the Python "discussion" forum was shut down. That does not sound like everyone except for the proponents is supposed to be heard (or is even aware of the discussion).
Re:No-GIL mode coming for Python
by usrbinbash on Sunday July 30, 2023 @08:39AM
(#36930568)
> No, for C/C++ you don't have to do anything
Even for such stable languages, a library maintainer has to, at the very least, patch security problems as they are discovered.
> That does not sound like everyone except for the proponents is supposed to be heard (or is even aware of the discussion).
There is an official poll among the Python core devs, linked in the article, which shows overwhelming support for the change. Since they are the ones who have to work this out, that's the only discussion about this that is relevant.
"We also need to bring along the rest of the Python community as we gain those insights and make sure the changes we want to make, and the changes we want them to make, are palatable."
End quote.
Yes, library developers have to keep up with developments in the underlying language as well as changes in usage patterns by the community. That is true for all programming languages.
And as I have pointed out numerous times before, this change is on the wishlist of many libdevs in the python community.