<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Python Threads and the Global Interpreter Lock</title>
	<atom:link href="http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/feed/" rel="self" type="application/rss+xml" />
	<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/</link>
	<description>python, programming and other things</description>
	<lastBuildDate>Sun, 04 Mar 2012 06:06:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tier 1 Sell-Side Language War: Slang vs Python vs Scala &#171; Tales from a Trading Desk</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-161603</link>
		<dc:creator>Tier 1 Sell-Side Language War: Slang vs Python vs Scala &#171; Tales from a Trading Desk</dc:creator>
		<pubDate>Mon, 28 Nov 2011 12:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-161603</guid>
		<description>[...] the Python financial world I suspect a lot more developers are now aware of the Global Interpreter Lock (GIL), especially given the calculations and threading nature of front-office solutions. Reading on [...]</description>
		<content:encoded><![CDATA[<p>[…] the Python financial world I suspect a lot more developers are now aware of the Global Interpreter Lock (GIL), especially given the calculations and threading nature of front-office solutions. Reading on […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Can a Python runtime environment be multithreaded? - Quora</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-161578</link>
		<dc:creator>Can a Python runtime environment be multithreaded? - Quora</dc:creator>
		<pubDate>Wed, 09 Nov 2011 00:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-161578</guid>
		<description>[...] involved in the multiprocessing package) that explains GIL, threads and processes in python clearly.http://jessenoller.com/2009/02/0...I found it useful.This answer .Please specify the necessary improvements.&#160;Edit Link Text Show [...]</description>
		<content:encoded><![CDATA[<p>[…] involved in the multiprocessing package) that explains GIL, threads and processes in python clearly.<a href="http://jessenoller.com/2009/02/0" rel="nofollow">http://jessenoller.com/2009/02/0</a>…I found it useful.This answer .Please specify the necessary improvements. Edit Link Text Show […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I thread Python ed il Global Interpreter Lock &#171; MasciBlog</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-68343</link>
		<dc:creator>I thread Python ed il Global Interpreter Lock &#171; MasciBlog</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-68343</guid>
		<description>[...] http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/ [...]</description>
		<content:encoded><![CDATA[<p>[…] <a href="http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/" rel="nofollow">http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/</a> […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mads</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-139112</link>
		<dc:creator>Mads</dc:creator>
		<pubDate>Wed, 25 Mar 2009 13:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-139112</guid>
		<description>Excellent article! I was wondering why my stackless python code would not let me utilize my multi-core CPU fully, and your article explains it with great clarity. Thank you.</description>
		<content:encoded><![CDATA[<p>Excellent article! I was wondering why my stackless python code would not let me utilize my multi-core CPU fully, and your article explains it with great clarity. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mads</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-68330</link>
		<dc:creator>Mads</dc:creator>
		<pubDate>Wed, 25 Mar 2009 09:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-68330</guid>
		<description>Excellent article! I was wondering why my stackless python code would not let me utilize my multi-core CPU fully, and your article explains it with great clarity. Thank you.</description>
		<content:encoded><![CDATA[<p>Excellent article! I was wondering why my stackless python code would not let me utilize my multi-core CPU fully, and your article explains it with great clarity. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Masci</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-68094</link>
		<dc:creator>Masci</dc:creator>
		<pubDate>Fri, 20 Mar 2009 14:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-68094</guid>
		<description>Thanks for your article, I found it clear and fun and I think it could be a precious resource for those who visit Thread Land for the first time ;-)&lt;br&gt;Jesse, any objection if I translate it in italian?</description>
		<content:encoded><![CDATA[<p>Thanks for your article, I found it clear and fun and I think it could be a precious resource for those who visit Thread Land for the first time ;-)<br />Jesse, any objection if I translate it in italian?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-67917</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 18 Mar 2009 01:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-67917</guid>
		<description>Great article; thank you. I hope to read more on this issue so keep up the posts!</description>
		<content:encoded><![CDATA[<p>Great article; thank you. I hope to read more on this issue so keep up the posts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sal</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-66057</link>
		<dc:creator>Sal</dc:creator>
		<pubDate>Mon, 23 Feb 2009 02:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-66057</guid>
		<description>As a fairly new Python user, I found your article to be very helpful. It helped me understand the pros and cons of threading in Python and put concurrency into context. Thank you.</description>
		<content:encoded><![CDATA[<p>As a fairly new Python user, I found your article to be very helpful. It helped me understand the pros and cons of threading in Python and put concurrency into context. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea Grandi</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-65897</link>
		<dc:creator>Andrea Grandi</dc:creator>
		<pubDate>Fri, 20 Feb 2009 21:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-65897</guid>
		<description>You say &quot;The banality of the code notwithstanding, one of the two tests will always fail&quot;. It&#039;s not complete/exact: both can be FALSE. I run this code on my machine and I get a FALSE / FALSE every 20-30 times.</description>
		<content:encoded><![CDATA[<p>You say “The banality of the code notwithstanding, one of the two tests will always fail”. It’s not complete/exact: both can be FALSE. I run this code on my machine and I get a FALSE / FALSE every 20–30 times.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mailund on the Internet &#187; Blog Archive &#187; This week in the blogs</title>
		<link>http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/comment-page-1/#comment-64610</link>
		<dc:creator>Mailund on the Internet &#187; Blog Archive &#187; This week in the blogs</dc:creator>
		<pubDate>Sun, 08 Feb 2009 10:53:39 +0000</pubDate>
		<guid isPermaLink="false">http://jessenoller.com/?p=447#comment-64610</guid>
		<description>[...] Python threads and the global interpreter lock (Jesse Noller) [...]</description>
		<content:encoded><![CDATA[<p>[…] Python threads and the global interpreter lock (Jesse Noller) […]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Object Caching 725/725 objects using disk: basic

Served from: jessenoller.com @ 2012-05-22 07:59:36 -->
