On Wed, Jul 30, 2014 at 6:11 PM, Matthew Brett <matthew.br...@gmail.com>
wrote:
> But - for exploring plotting, I would say it was a good choice.
Yup, I'm obviously as biased as they come, but I think that the immediate
feedback and the ability to keep plots together with their source code,
makes learning and experimenting with mpl (or other plotting libs) an ideal
use case for the notebook.
The only catch to be aware of is that, in order for a simple
plot(x)
to produce a figure without having to manually call show(), we do a bit of
magic behind the scenes. And that magic can occasionally lead to duplicate
figures when you start manually calling display(fig) yourself. So in that
more advanced scenario, you will need to add the occasional plt.close()
call.
HTH,
f
--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
