<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Atom Publishing Protocol: Atompub</title>
	<link>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/</link>
	<description></description>
	<pubDate>Mon, 01 Dec 2008 21:48:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Martijn Faassen</title>
		<link>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-140</link>
		<dc:creator>Martijn Faassen</dc:creator>
		<pubDate>Mon, 13 Aug 2007 15:54:48 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-140</guid>
		<description>Concerning naming: I wish we had a different name for our package database than PyPi, which is impossible to keep straight with PyPy. Nobody expects that the "Py" in PyPI should be pronounced differently than the "Py" anywhere else, including "PyPy", and due to the math heritage people will be likely to proncoune 'pi' the same way as well.

By the way, I also wish that our package installation tool hadn't been called "easy_install". It's an overly generic name that doesn't set up any associations with Python.</description>
		<content:encoded><![CDATA[<p>Concerning naming: I wish we had a different name for our package database than PyPi, which is impossible to keep straight with PyPy. Nobody expects that the &#8220;Py&#8221; in PyPI should be pronounced differently than the &#8220;Py&#8221; anywhere else, including &#8220;PyPy&#8221;, and due to the math heritage people will be likely to proncoune &#8216;pi&#8217; the same way as well.</p>

<p>By the way, I also wish that our package installation tool hadn&#8217;t been called &#8220;easy_install&#8221;. It&#8217;s an overly generic name that doesn&#8217;t set up any associations with Python.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-134</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Mon, 13 Aug 2007 01:06:49 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-134</guid>
		<description>Yeah, I actually just put something together this weekend: [FlatAtomPub](http://svn.pythonpaste.org/Paste/apps/FlatAtomPub/trunk) -- it really needs a database to scale at all well (it's purely flat files currently), but otherwise it all came together pretty quickly.  [APE](http://www.tbray.org/ape/) was a big help.</description>
		<content:encoded><![CDATA[<p>Yeah, I actually just put something together this weekend: <a href="http://svn.pythonpaste.org/Paste/apps/FlatAtomPub/trunk">FlatAtomPub</a> &#8212; it really needs a database to scale at all well (it&#8217;s purely flat files currently), but otherwise it all came together pretty quickly.  <a href="http://www.tbray.org/ape/">APE</a> was a big help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrey Nordin</title>
		<link>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-133</link>
		<dc:creator>Andrey Nordin</dc:creator>
		<pubDate>Mon, 13 Aug 2007 00:57:12 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2007/08/12/atom-publishing-protocol-atompub/#comment-133</guid>
		<description>Yes, Atompub sounds better than APP and is more suitable for searching. And it's the name of the [Atompub spec draft](http://tools.ietf.org/html/draft-ietf-atompub-protocol) of course. I'm with Atompub since 2005 and I'm glad that many developers are going to use it in their RESTful publishing projects. I guess you're writing Atompub stuff in Python, aren't you?</description>
		<content:encoded><![CDATA[<p>Yes, Atompub sounds better than APP and is more suitable for searching. And it&#8217;s the name of the <a href="http://tools.ietf.org/html/draft-ietf-atompub-protocol">Atompub spec draft</a> of course. I&#8217;m with Atompub since 2005 and I&#8217;m glad that many developers are going to use it in their RESTful publishing projects. I guess you&#8217;re writing Atompub stuff in Python, aren&#8217;t you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
