News for hackers. Stuff that matters.
Re:Our Plan for Python 3.13 by throwaway2037 on Friday June 16, 2023 @06:29AM (#36354274)
I too enjoyed the parent comment. It's right up there with "as soon as we have sufficiently smart enough compilers, that won't be an issue anymore".

I needed to Google SMOP, which tells me: "small matter of programming". Correct?

Re:Our Plan for Python 3.13 by phire on Friday June 16, 2023 @08:20AM (#36355381)
I'm confused. Why do people think my suggested solution is difficult enough to be comparable to the halting problem or "a smart enough compiler"?

We are talking about a scenario where cpython has already been modified to support both GIL and non-GIL operating modes, and a set of libraries that support the new non-GIL mode have been manually annotated by programmers.

All I'm suggesting is that on top of this, we modify the "load library" code to detect at runtime when we are loading a library that doesn't support the new non-GIL mode and switch modes.

Re:Our Plan for Python 3.13 by throwaway2037 on Friday June 16, 2023 @10:43PM (#36366708)
This simplest solution is to get a patch accepted by Python team. Good luck with that.
Re:Our Plan for Python 3.13 by Karellen on Friday June 16, 2023 @11:15AM (#36358008)
> I needed to Google SMOP, which tells me: "small matter of programming". Correct?

Yes, it can mean either "small..." or "simple matter of programming", which is more the meaning I had in mind. But either fit.