<?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: Give Winpdb a New Name</title>
	<atom:link href="http://winpdb.org/2007/11/give-winpdb-a-new-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/</link>
	<description></description>
	<pubDate>Thu, 11 Mar 2010 16:35:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: eddie</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-2/#comment-78847</link>
		<dc:creator>eddie</dc:creator>
		<pubDate>Sat, 13 Jun 2009 00:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-78847</guid>
		<description>...on reflection this connotation is a bit Brit-centric.  But it could also be used by Americans when bugs make them really angry...</description>
		<content:encoded><![CDATA[<p>&#8230;on reflection this connotation is a bit Brit-centric.  But it could also be used by Americans when bugs make them really angry&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eddie</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-2/#comment-78846</link>
		<dc:creator>eddie</dc:creator>
		<pubDate>Sat, 13 Jun 2009 00:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-78846</guid>
		<description>This discussion seems to have petered out and the old name remains!  The name for a python symbolic debugger for those of us who like a tipple or two has to be ... pysd</description>
		<content:encoded><![CDATA[<p>This discussion seems to have petered out and the old name remains!  The name for a python symbolic debugger for those of us who like a tipple or two has to be &#8230; pysd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bg</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-24557</link>
		<dc:creator>bg</dc:creator>
		<pubDate>Sun, 20 Jul 2008 00:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-24557</guid>
		<description>wxpdb?</description>
		<content:encoded><![CDATA[<p>wxpdb?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-9073</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Sun, 06 Apr 2008 17:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-9073</guid>
		<description>First thought was Pydeb.

But, Pysect is juicier.

happy brainstorming!</description>
		<content:encoded><![CDATA[<p>First thought was Pydeb.</p>
<p>But, Pysect is juicier.</p>
<p>happy brainstorming!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m--s</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-8222</link>
		<dc:creator>m--s</dc:creator>
		<pubDate>Thu, 20 Mar 2008 21:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-8222</guid>
		<description>PyDB-IDE
PyDB-GUI
gfxpdb
pdb-fx

... or any combination of these</description>
		<content:encoded><![CDATA[<p>PyDB-IDE<br />
PyDB-GUI<br />
gfxpdb<br />
pdb-fx</p>
<p>&#8230; or any combination of these</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alejandro Moreno</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-7629</link>
		<dc:creator>Alejandro Moreno</dc:creator>
		<pubDate>Sun, 09 Mar 2008 06:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-7629</guid>
		<description>Either completely descriptive (e.g. pdbui) or, as suggested by Ange on Nov. 23rd, completely made up (e.g. jadespy - graphical python debugger, or whatever)</description>
		<content:encoded><![CDATA[<p>Either completely descriptive (e.g. pdbui) or, as suggested by Ange on Nov. 23rd, completely made up (e.g. jadespy - graphical python debugger, or whatever)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lennart Regebro</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-6546</link>
		<dc:creator>Lennart Regebro</dc:creator>
		<pubDate>Thu, 14 Feb 2008 23:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-6546</guid>
		<description>EZ or easy == "no good" in most peoples eyes. Not a good option.</description>
		<content:encoded><![CDATA[<p>EZ or easy == &#8220;no good&#8221; in most peoples eyes. Not a good option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-6197</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 05 Feb 2008 22:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-6197</guid>
		<description>The name _must_ be changed.

"py" and "debug" should be in the new name.

If PyDebug is not available for adoption, then how about PyEzDebug?</description>
		<content:encoded><![CDATA[<p>The name _must_ be changed.</p>
<p>&#8220;py&#8221; and &#8220;debug&#8221; should be in the new name.</p>
<p>If PyDebug is not available for adoption, then how about PyEzDebug?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: homunq</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-6191</link>
		<dc:creator>homunq</dc:creator>
		<pubDate>Tue, 05 Feb 2008 13:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-6191</guid>
		<description>... although on further consideration, winPdb is not so violent, it's more like a microscope. But pycroscope is strained, pyscope is not as snappy, and pyEye is taken. pyBugBox (or pBB) is an option - to me, a bug box is a transparent box with a magifier in the lid for looking at bugs, though Google doesn't immediately back me up. 

I still think pySwatter is probably the best - immediately suggests an icon, too.</description>
		<content:encoded><![CDATA[<p>&#8230; although on further consideration, winPdb is not so violent, it&#8217;s more like a microscope. But pycroscope is strained, pyscope is not as snappy, and pyEye is taken. pyBugBox (or pBB) is an option - to me, a bug box is a transparent box with a magifier in the lid for looking at bugs, though Google doesn&#8217;t immediately back me up. </p>
<p>I still think pySwatter is probably the best - immediately suggests an icon, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: homunq</title>
		<link>http://winpdb.org/2007/11/give-winpdb-a-new-name/comment-page-1/#comment-6190</link>
		<dc:creator>homunq</dc:creator>
		<pubDate>Tue, 05 Feb 2008 13:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://winpdb.org/?p=33#comment-6190</guid>
		<description>My vote goes to pySwatter, because it's a simple tool.</description>
		<content:encoded><![CDATA[<p>My vote goes to pySwatter, because it&#8217;s a simple tool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
