News for hackers. Stuff that matters.
Re:Let's Remove the Global Interpreter Lock by taeric on Monday August 14, 2017 @11:52AM (#15009551)
There is a clear difference here, though. Making a change that could lead to poorly written libraries now being broken is clearly the fault of the change. Userspace for these libraries is defined by how it is, not how it was intended.

(And really, was it intended to be dangerous in this way?)

Re:Let's Remove the Global Interpreter Lock by masklinn on Monday August 14, 2017 @12:01PM (#15009636)
> There is a clear difference here, though. Making a change that could lead to poorly written libraries now being broken is clearly the fault of the change.

No, these libraries are already semantically broken in the same way e.g. libraries which didn't properly close their files and assumed the CPython refcounting GC would wipe there asses were broken.

They're already broken under two non-GIL'd implementations.

Re:Let's Remove the Global Interpreter Lock by cjhanks on Monday August 14, 2017 @01:28PM (#15010530)
I agree. Even developers who are well aware of how to write thread-safe code probably don't even bother with mutex locking in Python. That code isn't poorly written... it's just code targeting the implementation.
Re:Let's Remove the Global Interpreter Lock by koolba on Monday August 14, 2017 @12:03PM (#15009668)
No the fault in that situation is a user blindly upgrading PyPy without testing the totality of their software package and its dependencies.

Expecting bad code to magically work forever is unrealistic and hinders progress.

Re:Let's Remove the Global Interpreter Lock by rguillebert on Monday August 14, 2017 @12:45PM (#15010114)
Then just use the version of PyPy with a GIL?