[IPython-dev] Bumping up priority of thinking about output scrolling/control

Brian Granger ellisonbg at gmail.com
Thu May 31 23:22:35 EDT 2012


i can look into this.  But the other option for the output of multiple
engines is to build a simple widget that has a slider and allows you
the slide through the output of the different engines.  But I agree
that we need a more general solution to this issue.

On Thu, May 31, 2012 at 7:55 PM, Fernando Perez <fperez.net at gmail.com> wrote:
> Hey,
>
> Running code with %%px on 16 engines that had been wired to spit
> stdout by default is quickly making me think about a discussion we
> started earlier:
>
> https://github.com/ipython/ipython/issues/1553
>
> Now that the 'big three' have landed, I think we can begin to scope
> what a 0.13 release would involve, and I'd *really* like to have some
> kind of solution for this.  As Titus indicated in Boulder, without
> this some of his use cases were really unmanageable in practice, and
> I'm getting pretty close to that right now too...
>
> Bright ideas?
>
> f
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev



-- 
Brian E. Granger
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu and ellisonbg at gmail.com



More information about the IPython-dev mailing list