<?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"
	>
<channel>
	<title>Comments on: Numerical Python versus SciPy core</title>
	<atom:link href="http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/</link>
	<description>Daniel Lemire's blog is about life in academia, research in Computer Science, wondering how we can reconcile fast databases and algorithms with the informal and asemantic nature of the world around us. It is broadcasted from Montreal (Canada).</description>
	<pubDate>Thu, 20 Nov 2008 23:35:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Travis Oliphant</title>
		<link>http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/#comment-3547</link>
		<dc:creator>Travis Oliphant</dc:creator>
		<pubDate>Sat, 31 Dec 2005 07:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/#comment-3547</guid>
		<description>The inline docstrings are *not* missing.  Everything from Numeric is there along with new docstrings for new functionality.  Please don't spread misinformation.   

You may disagree with the name changes.  If you do, chime in on the mailing lists and let your voice be heard.  We are very responsive to users. 

If there is enough demand for it, it would be extremely easy to create compatibility modules. 

The reality is nobody is maintaing Numeric anymore.  While it is still useful, it is dying. It will not keep up with newer versions of Python.  The great thing about open source is you can still use it if you want, but your peers are moving to something else.</description>
		<content:encoded><![CDATA[<p>The inline docstrings are *not* missing.  Everything from Numeric is there along with new docstrings for new functionality.  Please don&#8217;t spread misinformation.   </p>
<p>You may disagree with the name changes.  If you do, chime in on the mailing lists and let your voice be heard.  We are very responsive to users. </p>
<p>If there is enough demand for it, it would be extremely easy to create compatibility modules. </p>
<p>The reality is nobody is maintaing Numeric anymore.  While it is still useful, it is dying. It will not keep up with newer versions of Python.  The great thing about open source is you can still use it if you want, but your peers are moving to something else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tristram Brelstaff</title>
		<link>http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/#comment-3306</link>
		<dc:creator>Tristram Brelstaff</dc:creator>
		<pubDate>Sat, 19 Nov 2005 09:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.daniel-lemire.com/blog/archives/2005/11/17/numerical-python-versus-scipy-core/#comment-3306</guid>
		<description>I'd feel tempted to create an intermediate module LinearAlgebra.py just containing the single line "import scipy.linalg.*".  I agree that such naming issues can be very annoying.  It is very 1960's FORTRAN to abbreviate names to six characters.</description>
		<content:encoded><![CDATA[<p>I&#8217;d feel tempted to create an intermediate module LinearAlgebra.py just containing the single line &#8220;import scipy.linalg.*&#8221;.  I agree that such naming issues can be very annoying.  It is very 1960&#8217;s FORTRAN to abbreviate names to six characters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
