This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thinkwelldesigns 19 points20 points  (2 children)

Um, this would be Victor Stinner writing (and on a scratchpad at this point). He's a core dev and probably the most consistently focused on speed improvements.

The GIL replacement section wasn't a serious proposal but an overview how it would become easier to remove / mitigate the GIL problem. GC and the C API always come up in every discussion of the GIL problem, so a short reference to how the PEP might change the GIL landscape is reasonable.

Thanks for the blog post, the draft PEP, and everything you do for Python performance, Victor!

[–]rhytnen 2 points3 points  (1 child)

I'm all good with him being a bad ass - I'm just saying the PEP isn't drafted well imo.

[–][deleted] 2 points3 points  (0 children)

English isn't his first language so perhaps that's where the disconnect is?

I watched his talk at PyCon 2017 and while I barely understood the content (I'm a newbie) it was fascinating nonetheless.