http://guaka.org/tag/numpy en http://guaka.org/2007/10/04/numpy-documentation <div class="field field-name-taxonomy-vocabulary-2 field-type-taxonomy-term-reference field-label-above clearfix"><h3 class="field-label">tag: </h3><ul class="links"><li class="taxonomy-term-reference-0"><a href="/tag/attribution">attribution</a></li><li class="taxonomy-term-reference-1"><a href="/tag/creativecommons">creative_commons</a></li><li class="taxonomy-term-reference-2"><a href="/tag/graphs">graphs</a></li><li class="taxonomy-term-reference-3"><a href="/tag/money">money</a></li><li class="taxonomy-term-reference-4"><a href="/tag/noncommercial">noncommercial</a></li><li class="taxonomy-term-reference-5"><a href="/tag/numpy">numpy</a></li><li class="taxonomy-term-reference-6"><a href="/tag/prediction">prediction</a></li><li class="taxonomy-term-reference-7"><a href="/tag/python">Python</a></li><li class="taxonomy-term-reference-8"><a href="/tag/scientificcommunity">scientific_community</a></li><li class="taxonomy-term-reference-9"><a href="/tag/softwaredocumentation">software_documentation</a></li><li class="taxonomy-term-reference-10"><a href="/tag/trustmetrics">trust_metrics</a></li></ul></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even">With <a href="http://trustlet.org" target="_blank">trustlet</a>, I'm finally getting to a point where we can do cool stuff, evaluating prediction graphs of trust metrics. Now I need to refresh my Python array stuff. Since last time I was using that stuff, in 2004, they have refactored it (once more) and called it numpy. That's fine. But, in order to read an important part of the <a href="http://www.scipy.org/Documentation" target="_blank">documentation</a> you need to pay 39.99 US$. Now, that's <a href="http://finance.yahoo.com/currency/convert?amt=1&amp;from=CAD&amp;to=USD&amp;submit=Convert" title="CA$ &gt; US$">less and less</a>  by the day, but still, it's very inconvenient, and probably holding back wider acceptation of  Python in the scientific community. Like software, documentation should be free. I might even pay if the author would have chosen to use the <a href="http://creativecommons.org/licenses/by-nc-sa/">Creative Commons ShareAlike NonCommercial Attribution</a> license - but then I would be able to pass on the information to my friends (even they are all over the internet). I think it would have been a wiser choice to find a job at some institute or company to further the development of numpy and scipy, and its documentation in a freer way. That <a href="http://www.oreillynet.com/onlamp/blog/2005/12/python_creator_guido_van_rossu.html" title="Python creator working for Google" target="_blank">shouldn't be too hard</a> these days.</div></div></div> Thu, 04 Oct 2007 00:08:39 +0000 Guaka 181 at http://guaka.org