<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Moratorium on Python language changes?</title>
	<link>http://ramblings.timgolden.me.uk/2009/10/22/moratorium-on-python-language-changes/</link>
	<description>The ramblings of Tim Golden</description>
	<pubDate>Thu, 09 Sep 2010 08:45:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Michael Dillon</title>
		<link>http://ramblings.timgolden.me.uk/2009/10/22/moratorium-on-python-language-changes/#comment-1029</link>
		<author>Michael Dillon</author>
		<pubDate>Thu, 22 Oct 2009 17:04:50 +0000</pubDate>
		<guid>http://ramblings.timgolden.me.uk/2009/10/22/moratorium-on-python-language-changes/#comment-1029</guid>
		<description>Hopefully some of that effort that goes "elsewhere" will go into creating a second tier Python toolbox, stuff that is not in the standard library, and probably will never be, but which we consider to be some form of best practice. This could be things like Beautiful Soup, or redis, or M2crypto.

Some of these third party projects have difficulty keeping up with newer CPython versions, and even where the module does not make sense on Jython or IronPython, it would be good to have a standard shim to access native Java or .NET libraries through the same interface. This would improve the portability of Python applications.</description>
		<content:encoded><![CDATA[<p>Hopefully some of that effort that goes &#8220;elsewhere&#8221; will go into creating a second tier Python toolbox, stuff that is not in the standard library, and probably will never be, but which we consider to be some form of best practice. This could be things like Beautiful Soup, or redis, or M2crypto.</p>
<p>Some of these third party projects have difficulty keeping up with newer CPython versions, and even where the module does not make sense on Jython or IronPython, it would be good to have a standard shim to access native Java or .NET libraries through the same interface. This would improve the portability of Python applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j_king</title>
		<link>http://ramblings.timgolden.me.uk/2009/10/22/moratorium-on-python-language-changes/#comment-1028</link>
		<author>j_king</author>
		<pubDate>Thu, 22 Oct 2009 13:57:03 +0000</pubDate>
		<guid>http://ramblings.timgolden.me.uk/2009/10/22/moratorium-on-python-language-changes/#comment-1028</guid>
		<description>I've been told that having an implementation be the standard for a language is stupid. I tend to agree; it makes the language a moving target for alternate implementations and restricts a lot of what they could do.

Standardize the syntax and let the developers create better implementations.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been told that having an implementation be the standard for a language is stupid. I tend to agree; it makes the language a moving target for alternate implementations and restricts a lot of what they could do.</p>
<p>Standardize the syntax and let the developers create better implementations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
