3 ms·
> all you really need to do is [SMOP]. But it's a very solvable problem. Awesome! I look forward to seeing your PR shortly. ;-)
by Karellen 3y ago
> all you really need to do is [SMOP]. But it's a very solvable problem.
Awesome! I look forward to seeing your PR shortly. ;-)
- throwaway2037 3y agoI 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?
- phire 3y agoI'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.
- throwaway2037 3y agoThis simplest solution is to get a patch accepted by Python team. Good luck with that.
- Karellen 3y ago> 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.