<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about scipy)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/scipy.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:19 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>SciPy at 1.0</title><link>https://sgillies.net/2017/10/25/scipy-at-1-0.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;SciPy 1.0 was &lt;a class="reference external" href="https://mail.python.org/pipermail/scipy-dev/2017-October/022235.html"&gt;announced this morning&lt;/a&gt;. Ralf
Gommers wrote:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;A version number should reflect the maturity of a project - and SciPy was
a mature and stable library that is heavily used in production settings for
a long time already.  From that perspective, the 1.0 version number is long
overdue.&lt;/p&gt;
&lt;p&gt;Some key project goals, both technical (e.g. Windows wheels and continuous
integration) and organisational (a governance structure, code of conduct
and a roadmap), have been achieved recently.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The code of conduct he mentions is here:
&lt;a class="reference external" href="https://github.com/scipy/scipy/blob/master/doc/source/dev/conduct/code_of_conduct.rst"&gt;https://github.com/scipy/scipy/blob/master/doc/source/dev/conduct/code_of_conduct.rst&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It's been interesting lurking in the code of conduct discussions on scipy-dev
and on GitHub. The project used a few existing CoCs as starting points
(including the Contributor Covenant used at Mapbox) and ended up with something
they felt more suited to their community.&lt;/p&gt;</description><category>community</category><category>conduct</category><category>numpy</category><category>scipy</category><category>work</category><guid>https://sgillies.net/2017/10/25/scipy-at-1-0.html</guid><pubDate>Wed, 25 Oct 2017 15:14:22 GMT</pubDate></item><item><title>SciPy Conference</title><link>https://sgillies.net/2014/07/13/scipy-conference.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I'm back from my first ever trip to SciPy, the annual scientific Python community
conference. I found it quite amazingly good.&lt;/p&gt;
&lt;img alt="https://conference.scipy.org/scipy2014/site_media/static/img/scipy2014_logo_simple.png" src="https://conference.scipy.org/scipy2014/site_media/static/img/scipy2014_logo_simple.png"&gt;
&lt;p&gt;Slides from my talk on Wednesday are at
&lt;a class="reference external" href="https://sgillies.github.io/scipy-2014-rasterio/"&gt;https://sgillies.github.io/scipy-2014-rasterio/&lt;/a&gt;. I feel like it went well and
hope that you found (and will find it) useful, too. I missed Tuesday's
sessions, which were jam packed with geospatial talks, and didn't have time to
check out all the slides from those before presenting. Referencing other talks
is something I usually try to do, and failing to do so felt a little weird. My
talk was sandwiched between Tyler Erickson's on Google Earth Engine and Shawn
Walbridge's on workflows and distribution of GIS Science toolkits; a nice
showing of research and science going on at Google, Mapbox, and Esri.&lt;/p&gt;
&lt;p&gt;The IPython Notebook seemed to be the major touchstone for presenters and other
attendees of the conference, and rightly so. I've got all kinds of plans for
doing things with it, many that I expressed at the conference, and I'm certain
that it's going to spread in GIS circles. Features coming soon to notebooks
near you include: map interactivity, Native Client notebooks, Google Drive
hosted notebooks, and a new &lt;a class="reference external" href="https://speakerdeck.com/fperez/project-jupyter"&gt;language agnostic platform&lt;/a&gt;. I enjoyed getting to meet
Fernando Perez and Brian Granger and congratulate them on the success of the
project.&lt;/p&gt;
&lt;p&gt;Greg Wilson's keynote, &lt;a class="reference external" href="https://www.youtube.com/watch?v=1e26rp6qPbA"&gt;available on Youtube&lt;/a&gt;, was a challenge to apply science to the teaching of programming and other
subjects. I definitely recommend watching it. A strange recommendation from me, I
know, since I'm more likely to say things like "keynotes are terrible." Keynotes
that stroke the audience are terrible. Wilson's is better than that.&lt;/p&gt;
&lt;p&gt;Best part of the trip for me was sprinting on GeoPandas and other projects with
Kelsey Jordahl, Nora Deram, Jacob Wasserman (remotely), Matt Perry, Taylor
Oshan, Carson Farmer, Shawn Walbridge, Serge Ray, and Philip Stephens. I learned
a ton about Pandas and GeoPandas, made some solid contributions to the project, and
all in great company. It was a pleasure and a privilege.&lt;/p&gt;
&lt;p&gt;One sobering thing is being reminded that not everyone enjoys the same pleasure
and privilege. It's important to read and think about April Wright's thoughts
on SciPy: &lt;a class="reference external" href="http://wrightaprilm.github.io/posts/lonely.html"&gt;http://wrightaprilm.github.io/posts/lonely.html&lt;/a&gt;.&lt;/p&gt;</description><category>esri</category><category>google</category><category>mapbox</category><category>privilege</category><category>python</category><category>rasterio</category><category>scipy</category><category>work</category><guid>https://sgillies.net/2014/07/13/scipy-conference.html</guid><pubDate>Sun, 13 Jul 2014 06:00:00 GMT</pubDate></item></channel></rss>