<?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 logging and performance: how to have your cake and eat it too</title>
	<atom:link href="http://dound.com/2010/02/python-logging-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://dound.com/2010/02/python-logging-performance/</link>
	<description>dound&#039;s space on the web</description>
	<lastBuildDate>Sun, 25 Jul 2010 21:17:31 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Underhill</title>
		<link>http://dound.com/2010/02/python-logging-performance/comment-page-1/#comment-6529</link>
		<dc:creator>David Underhill</dc:creator>
		<pubDate>Mon, 07 Jun 2010 21:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://dound.com/?p=268#comment-6529</guid>
		<description>&lt;a href=&quot;#comment-6528&quot; rel=&quot;nofollow&quot;&gt;@Evan Plaice&lt;/a&gt; 
Well, there was no Python preprocessor when I wrote this post anyway :).  It looks like a very useful tool.  For the specific task of removing particular logging statements, I&#039;ll stick to the script I posted here because I don&#039;t have to dirty my code with #ifdef&#039;s (it is also shorter than surrounding lots of logging blocks with #ifdef&#039;s).  But for more complicated scenario I think your preprocessor tool would be handy.  Thanks for sharing it!</description>
		<content:encoded><![CDATA[<p><a href="#comment-6528" rel="nofollow">@Evan Plaice</a><br />
Well, there was no Python preprocessor when I wrote this post anyway <img src='http://dound.com/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .  It looks like a very useful tool.  For the specific task of removing particular logging statements, I&#8217;ll stick to the script I posted here because I don&#8217;t have to dirty my code with #ifdef&#8217;s (it is also shorter than surrounding lots of logging blocks with #ifdef&#8217;s).  But for more complicated scenario I think your preprocessor tool would be handy.  Thanks for sharing it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Plaice</title>
		<link>http://dound.com/2010/02/python-logging-performance/comment-page-1/#comment-6528</link>
		<dc:creator>Evan Plaice</dc:creator>
		<pubDate>Mon, 07 Jun 2010 17:45:35 +0000</pubDate>
		<guid isPermaLink="false">http://dound.com/?p=268#comment-6528</guid>
		<description>&quot;there is no Python preprocessor&quot;

I wrote pypreprocessor to solve this issue. 

Check it out on Google code @:
http://code.google.com/p/pypreprocessor/</description>
		<content:encoded><![CDATA[<p>&#8220;there is no Python preprocessor&#8221;</p>
<p>I wrote pypreprocessor to solve this issue. </p>
<p>Check it out on Google code @:<br />
<a href="http://code.google.com/p/pypreprocessor/" rel="nofollow">http://code.google.com/p/pypreprocessor/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
