Date: Wed, 9 Jan 2008 21:46:12 -0500 From: "Michael P. Soulier" <msoulier@digitaltorque.ca> To: Danny Pansters <danny@ricin.com> Cc: Gunther Mayer <gunther.mayer@googlemail.com>, freebsd-questions@freebsd.org Subject: Re: Python threading - some ports depend on it, others break with it Message-ID: <20080110024612.GE6375@piglet.digitaltorque.ca> In-Reply-To: <200801100202.17511.danny@ricin.com> References: <47851504.8090006@gmail.com> <200801100202.17511.danny@ricin.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 10/01/08 Danny Pansters said: > It's my understanding that threading *in* python works well, but threading > *with* python doesn't and you shouldn't use/rely on it. I'm afraid I can't > tell you much more without an hour of googling and I wouldn't be sure if I > can adequately explain after. I think it has to do with the GIL. > > I suggest to ask at freebsd-python@freebsd.org. Threading in Python works fine in my experience, even using native threads. It is not very efficient on multi-core systems though, due to the GIL (global interpreter lock). Mike -- Michael P. Soulier <msoulier@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHhYb0KGqCc1vIvggRAo6qAKCrxru0CrjaWA+XNsjfp5cm2q9CogCffcuU hcgtY3mGdwcsMU+SXfHc7ZY= =x6Uv -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080110024612.GE6375>