Yes, there is an issue. I wouldn’t expect the core devs to implement this soon since currently all of their time is being spent on core issues like scalability and bug fixing. Most new features seem to come from contributors. A bug bounty might be a way to incentivize someone adding this feature.
No worries, I’m sure Norton Utilities will fix it.
For those wondering what PEP 703 is:
CPython’s global interpreter lock (“GIL”) prevents multiple threads from executing Python code at the same time. The GIL is an obstacle to using multi-core CPUs from Python efficiently. This PEP proposes adding a build configuration (–disable-gil) to CPython to let it run Python code without the global interpreter lock and with the necessary changes needed to make the interpreter thread-safe.
I don’t think Lemmy instance admins are colluding in a secret underground lair like a group of supervillains. There is no point since the decision of one has no impact on the others.
Second, many of us aren’t here for the “features”, we’re here for the freedom.
My personal opinion is that I have no problem if my instance federates with Threads as long as the interactions are a net positive for us. If Threads users prove to be abusive then I have no problem defederating with them.
In C/C++, undefined should be the meme of the little girl smiling while the house burns down behind her.
This is the way.
Come on, Python 2 only has 16 critical vulnerabilities. Live dangerously 🙃.
Wow, that is insanely helpful, thanks!