<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 9, 2013 at 8:10 PM, Aaron Meurer <span dir="ltr"><<a href="mailto:asmeurer@gmail.com" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=asmeurer@gmail.com&cc=&bcc=&su=&body=','_blank');return false;">asmeurer@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I noticed that git says "2.0.0-dev". Are you being overly optimistic,<br>
or did you revert your policy of only supporting one version at a<br>
time?<br></blockquote><div><br></div><div>I'm not sure what you mean. We are certainly planning to make backward-incompatible changes to be released in the Fall, which suggests a new major version. We are trying out a roughly six month major release cycle (2.0 in Winter, 3.0 next Summer). We will backport fixes to 1.0 as long as it is tenable (1.x branch already has a few fixes), which may not be past Winter.</div>
<div><br></div><div>-MinRK</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Aaron Meurer<br>
</font></span><div class="im HOEnZb"><br>
On Thu, Aug 8, 2013 at 7:35 PM, Fernando Perez <<a href="mailto:fperez.net@gmail.com" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=fperez.net@gmail.com&cc=&bcc=&su=&body=','_blank');return false;">fperez.net@gmail.com</a>> wrote:<br>
</div><div class="HOEnZb"><div class="h5">> Hi all,<br>
><br>
> I am incredibly thrilled, on behalf of the amazing IPython Dev Team,<br>
> to announce the official release of IPython 1.0 today, an effort<br>
> nearly 12 years in the making. The previous version (0.13) was<br>
> released on June 30, 2012, and in this development cycle we had:<br>
><br>
> ~12 months of work.<br>
> ~700 pull requests merged.<br>
> ~600 issues closed (non-pull requests).<br>
> contributions from ~150 authors.<br>
> ~4000 commits.<br>
><br>
><br>
> # A little context<br>
><br>
> What does "1.0" mean for IPython? Obviously IPython has been a staple<br>
> of the scientific Python community for years, and we've made every<br>
> effort to make it a robust and production ready tool for a long time,<br>
> so what exactly do we mean by tagging this particular release as 1.0?<br>
> Basically, we feel that the core design of IPython, and the scope of<br>
> the project, is where we want it to be.<br>
><br>
> What we have today is what we consider a reasonably complete, design-<br>
> and scope-wise, IPython 1.0: an architecture for interactive<br>
> computing, that can drive kernels in a number of ways using a<br>
> well-defined protocol, and rich and powerful clients that let users<br>
> control those kernels effectively. Our different clients serve<br>
> different needs, with the old workhorse of the terminal still being<br>
> very useful, but much of our current development energy going into the<br>
> Notebook, obviously. The Notebook enables interactive exploration to<br>
> become Literate Computing, bridging the gaps from individual work to<br>
> collaboration and publication, all with an open file format that is a<br>
> direct record of the underlying communication protocol.<br>
><br>
> There are obviously plenty of open issues (many of them very<br>
> important) that need fixing, and large and ambitious new lines of<br>
> development for the years to come. But the work of the last four<br>
> years, since the summer of 2009 when Brian Granger was able to devote<br>
> a summer (thanks to funding from the NiPy project - <a href="http://nipy.org" target="_blank">nipy.org</a>) to<br>
> refactoring the old IPython core code, finally opened up or<br>
> infrastructure for real innovation. By disentangling what was a useful<br>
> but impenetrable codebase, it became possible for us to start building<br>
> a flexible, modern system for interactive computing that abstracted<br>
> the old REPL model into a generic protocol that kernels could use to<br>
> talk to clients. This led at first to the creation of the Qt console,<br>
> and then to the Notebook and out-of-process terminal client. It also<br>
> allowed us to (finally!) unify our parallel computing machinery with<br>
> the rest of the interactive system, which Min Ragan-Kelley pulled off<br>
> in a development tour de force that involved rewriting in a few weeks<br>
> a huge and complex Twisted-based system.<br>
><br>
> We are very happy with how the Notebook work has turned out, and it<br>
> seems the entire community agrees with us, as the uptake has been<br>
> phenomenal. Back from the very first "IPython 0.0.1" that I started<br>
> in 2001:<br>
><br>
> <a href="https://gist.github.com/fperez/1579699" target="_blank">https://gist.github.com/fperez/1579699</a><br>
><br>
> there were already hints of tools like Mathematica: it was my everyday<br>
> workhorse as a theoretical physicist and I found its Notebook<br>
> environment invaluable. But as a grad student trying out "just an<br>
> afternoon hack" (IPython was my very first Python program as I was<br>
> learning the language), I didn't have the resources, skills or vision<br>
> to attempt building an entire notebook system, and to be honest the<br>
> tools of the day would have made that enterprise a miserable one. But<br>
> those ideas were always driving our efforts, and as IPython started<br>
> becoming a project with a team, we made multiple attempts to get a<br>
> good Notebook built around IPython. Those interested can read an old<br>
> blog post of mine with the history<br>
> (<a href="http://blog.fperez.org/2012/01/ipython-notebook-historical.html" target="_blank">http://blog.fperez.org/2012/01/ipython-notebook-historical.html</a>).<br>
> The short story is that in 2011, on our sixth attempt, Brian was again<br>
> able to devote a focused summer into using our client-server<br>
> architecture and, with the stack of the modern web (Javascript, CSS,<br>
> websockets, Tornado, ...), finally build a robust system for Literate<br>
> Computing across programming languages.<br>
><br>
> Today, thanks to the generous support and vision of Josh Greenberg at<br>
> the Alfred P. Sloan Foundation, we are working very hard on building<br>
> the notebook infrastructure, and this release contains major advances<br>
> on that front. We have high hopes for what we'll do next; as a<br>
> glimpse of the future that this enables, now there is a native Julia<br>
> kernel that speaks to our clients, notebook included:<br>
> <a href="https://github.com/JuliaLang/IJulia.jl" target="_blank">https://github.com/JuliaLang/IJulia.jl</a>.<br>
><br>
><br>
> # Team<br>
><br>
> I can't stress enough how impressed I am with the work people are<br>
> doing in IPython, and what a privilege it is to work with colleagues<br>
> like these. Brian Granger and Min Ragan-Kelley joined IPython around<br>
> 2005, initially working on the parallel machinery, but since ~ 2009<br>
> they have become the heart of the project. Today Min is our top<br>
> committer and knows our codebase better than anyone else, and I can't<br>
> imagine better partners for an effort like this.<br>
><br>
> And from regulars in our core team like Thomas Kluyver, Matthias<br>
> Bussonnier, Brad Froehle and Paul Ivanov to newcomers like Jonathan<br>
> Frederic and Zach Sailer, in addition to the many more whose names are<br>
> in our logs, we have a crazy amount of energy being poured into<br>
> IPython. I hope we'll continue to harness it productively!<br>
><br>
> The full list of contributors to this release can be seen here:<br>
><br>
> <a href="http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html" target="_blank">http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html</a><br>
><br>
><br>
> # Release highlights<br>
><br>
> * nbconvert: this is the major piece of new functionality in this<br>
> cycle, and was an explicit part of our roadmap<br>
> (<a href="https://github.com/ipython/ipython/wiki/Roadmap:-IPython" target="_blank">https://github.com/ipython/ipython/wiki/Roadmap:-IPython</a>). nbconvert<br>
> is now an IPython subcommand to convert notebooks into other formats<br>
> such as HTML or LaTeX, but more importantly, it's a very flexible<br>
> system that lets you write custom templates to generate new output<br>
> with arbitrary control over the formatting and transformations that<br>
> are applied to the input.<br>
><br>
> We want to stress that despite the fact that a huge amount of work<br>
> went into nbconvert, this should be considered a *tech preview*<br>
> release. We've come to realize how complex this problem is, and while<br>
> we'll make every effort to keep the high-level command-line syntax and<br>
> APIs as stable as possible, it is quite likely that the internals will<br>
> continue to evolve, possibly in backwards-incompatible ways. So if<br>
> you start building services and libraries that make heavy use of the<br>
> nbconvert internals, please be prepared for some turmoil in the months<br>
> to come, and ping us on the dev list with questions or concerns.<br>
><br>
> * Notebook improvements: there has been a ton of polish work in the<br>
> notebook at many levels, though the file format remains unchanged from<br>
> 0.13, so you shouldn't have any problems sharing notebooks with<br>
> colleagues still using 0.13.<br>
><br>
> - Autosave: probably the most oft-requested feature, the notebook<br>
> server now autosaves your files! You can still hit Ctrl-S to force a<br>
> manual save (which also creates a special 'checkpoint' you can come<br>
> back to).<br>
><br>
> - The notebook supports raw_input(), and thus also %debug. This was<br>
> probably the main deficiency of the notebook as a client compared to<br>
> the terminal/qtconsole, and it has been finally fixed.<br>
><br>
> - Add %%html, %%svg, %%javascript, and %%latex cell magics for<br>
> writing raw output in notebook cells.<br>
> - Fix an issue parsing LaTeX in markdown cells, which required users<br>
> to type \\\, instead of \\.<br>
> -Images support width and height metadata, and thereby 2x scaling<br>
> (retina support).<br>
> - %%file has been renamed %%writefile (%%file) is deprecated.<br>
><br>
> * The input transofrmation code has been updated and rationalized.<br>
> This is a somewhat specialized part of IPython, but of importance to<br>
> projects that build upon it for custom environments, like Sympy and<br>
> Sage.<br>
><br>
> Our full release notes are here:<br>
><br>
> <a href="http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/version1.0.html" target="_blank">http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/version1.0.html</a><br>
><br>
> and the gory details are here:<br>
><br>
> <a href="http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html" target="_blank">http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html</a><br>
><br>
><br>
> # Installation<br>
><br>
> Installation links and instructions are at: <a href="http://ipython.org/install.html" target="_blank">http://ipython.org/install.html</a><br>
> And IPython is also on PyPI: <a href="http://pypi.python.org/pypi/ipython" target="_blank">http://pypi.python.org/pypi/ipython</a><br>
><br>
><br>
> # Requirements<br>
><br>
> IPython 1.0 requires Python ≥ 2.6.5 or ≥ 3.2.1. It does not support<br>
> Python 3.0, 3.1, or 2.5.<br>
><br>
><br>
> # Acknowledgments<br>
><br>
> Last but not least, we'd like to acknowledge the generous support of<br>
> those who make it possible for us to spend our time working on<br>
> IPython. In particular, the Alfred P. Sloan Foundation today lets us<br>
> have a solid team working full-time on the project, and without the<br>
> support of Enthought Inc at multiple points in our history, we<br>
> wouldn't be where we are today.<br>
><br>
> The full list of our support is here:<br>
><br>
> <a href="http://ipython.org/index.html#support" target="_blank">http://ipython.org/index.html#support</a><br>
><br>
><br>
> Thanks to everyone! Please enjoy IPython 1.0, and report all bugs as usual!<br>
><br>
> Fernando, on behalf of the IPython Dev Team.<br>
><br>
> --<br>
> Fernando Perez (@fperez_org; <a href="http://fperez.org" target="_blank">http://fperez.org</a>)<br>
> fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)<br>
> fernando.perez-at-berkeley: contact me here for any direct mail<br>
> --<br>
> Fernando Perez (@fperez_org; <a href="http://fperez.org" target="_blank">http://fperez.org</a>)<br>
> fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)<br>
> fernando.perez-at-berkeley: contact me here for any direct mail<br>
> _______________________________________________<br>
> IPython-dev mailing list<br>
> <a href="mailto:IPython-dev@scipy.org" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=IPython-dev@scipy.org&cc=&bcc=&su=&body=','_blank');return false;">IPython-dev@scipy.org</a><br>
> <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=IPython-dev@scipy.org&cc=&bcc=&su=&body=','_blank');return false;">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
</div></div></blockquote></div><br></div></div>