Comments on: Python Warts, part 2 – the infamous GIL http://atlee.ca/blog/2006/06/27/python-warts-2/ programming, photography, media, and anything else that strikes my fancy Fri, 27 Jan 2012 19:08:24 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ian Bicking http://atlee.ca/blog/2006/06/27/python-warts-2/comment-page-1/#comment-4534 Ian Bicking Wed, 28 Jun 2006 01:46:10 +0000 http://atlee.ca/blog/2006/06/27/python-warts-2/#comment-4534 Note I never said that the current situation was perfect, or even very good. IPC is way harder in Python than it should be. So... """In the short term, some slick IPC would be nice, but in the long term a truly multithreaded Python interpreter would benefit everybody.""" I'd switch those: in the short term a truly multithreaded Python interpreter would be nice, but slick IPC in Python would benefit everybody. And it doesn't even require much (any?) interpreter work. Note I never said that the current situation was perfect, or even very good. IPC is way harder in Python than it should be. So…

“”"In the short term, some slick IPC would be nice, but in the long term a truly multithreaded Python interpreter would benefit everybody.”"”

I’d switch those: in the short term a truly multithreaded Python interpreter would be nice, but slick IPC in Python would benefit everybody. And it doesn’t even require much (any?) interpreter work.

]]>