<br><br><div class="gmail_quote">On Fri, Jan 6, 2012 at 9:17 AM, Fernando Perez <span dir="ltr">&lt;<a href="mailto:fperez.net@gmail.com">fperez.net@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">On Fri, Jan 6, 2012 at 3:44 AM, Thomas Kluyver &lt;<a href="mailto:takowl@gmail.com">takowl@gmail.com</a>&gt; wrote:<br>
</div><div class="im">&gt; Why are we recreating a notebook, when SAGE&#39;s already works? I expect other<br>
&gt; people will weigh in with different motivations, but first off, it works<br>
&gt; without a 400MB download ;-). SAGE is kind of an ecosystem of its own,<br>
&gt; bundling a lot of libraries into its package system. That has various<br>
&gt; consequences:<br>
&gt; - Linux distributions won&#39;t package SAGE, whereas soon you&#39;ll be able to do<br>
&gt; &quot;apt-get install ipython notebook&quot;<br>
&gt; - To run SAGE on Windows, you set up a virtual machine to run Linux. IPython<br>
&gt; can run natively.<br>
&gt; - SAGE ships its own copy of Python (by the looks of it, that&#39;s currently<br>
&gt; version 2.6.4). IPython can be installed on other versions, including Python<br>
&gt; 3.<br>
<br>
</div>All very valid and correct points, I&#39;ll provide some extra perspective<br>
in a separate reply.<br>
<div class="im"><br></div></blockquote><div>Yes, I agrees. On last item, I was surprised that I can&#39;t change Python version and compiler options inside SAGE configurations without breaking SAGE build. <br> <br></div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">
&gt; None of the above is criticising SAGE - the project has its own goals, and<br>
&gt; what they&#39;re doing makes sense for that. But for IPython, it&#39;s important to<br>
&gt; fit into the general Python landscape. Although we are in touch with SAGE,<br>
&gt; and hopefully there&#39;s room to collaborate and share code.<br>
<br>
</div>With the caveat Aaron mentioned, that sage being GPL, we must ask them<br>
for explicit permission if we want to reuse any of their code (and<br>
when we&#39;ve done so, they&#39;ve graciously agreed to relicense snippets as<br>
BSD). In contrast, sage can freely use code from ipython, which it<br>
does.<br>
<div class="im"><br>
&gt; I don&#39;t think inline Cython support is on the roadmap at present - it sounds<br>
&gt; like the sort of thing that would make for a good extension. If you&#39;re<br>
&gt; interested in writing one, have a look here:<br>
&gt; <a href="http://ipython.org/ipython-doc/stable/config/extensions/index.html" target="_blank">http://ipython.org/ipython-doc/stable/config/extensions/index.html</a><br>
<br>
</div>Actually I have a very concrete plan on how to enable sage-style<br>
&#39;cell-level magics&#39;. The only problem is that the entire draft is in<br>
my brain only and I haven&#39;t had the time to sit down and type it out.<br>
The priority for this is obviously going up, so I&#39;ll do my best to<br>
flush it soon.<br>
<br></blockquote><div>Sounds encouraging. <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Cheers,<br>
<br>
f<br>
</blockquote></div>Thank you for comprehensive replies, gents. <br>Oleg<br>