News for hackers. Stuff that matters.
Re:Celery, non-blocking code and quest against coroutines by theseatoms on Thursday June 09, 2016 @09:53AM (#11869353)
I'm curious.. in what way are cpython's data structures problematic? Do you just mean as they relate to the GIL design choice, and the downsides/limitations that follow from the overall design?
Re:Celery, non-blocking code and quest against coroutines by coldtea on Thursday June 09, 2016 @10:12AM (#11869480)
He probably means the internal datastructures of Python the language (interpreter), not the datastructures it exposes to the user (list, map, tuple, etc).
Re:Celery, non-blocking code and quest against coroutines by mdomans on Thursday June 09, 2016 @10:42AM (#11869675)
Yup. If you don't have to care about thread safety on API level, e.g. list, problems such as what's going on currently in gilectomy are no longer yours.
Re:Celery, non-blocking code and quest against coroutines by DasIch on Thursday June 09, 2016 @11:55AM (#11870218)
The GIL has atomic bytecodes as a side effect and this assumption has become part of the API.

There is nothing on the datastructure side that can be done to "fix" this.

In any case memory access should be considered a memory management problem just like allocating and freeing memory is. It needs to be solved on the language level to create sufficiently high level user experience.

You can only do that if you're willing to do things very differently such as Rusts Ownership/Borrowing approach.

Re:Celery, non-blocking code and quest against coroutines by markbnj on Thursday June 09, 2016 @11:07PM (#11874021)
Yes, this. Sorry I was away all day and didn't have time to reply.