Re: [matplotlib-devel] 1.4.0rc1 has been tagged
On 14 July 2014 00:10, Damon McDougall wrote: > On Sun, Jul 13, 2014 at 12:27 AM, Eric Firing wrote: > > On 2014/07/12, 7:20 PM, Thomas Caswell wrote: > >> Hey all, > >> > >> After a very productive sprint at scipy (according to pluse, we merged > >> 35 PRs in the last 3 days), I have created the 1.4.x branch and tagged > >> the first release candidate (1.4.0rc1). > >> > >> There are a good number of outstanding issues with documentation (re > >> the fate of pylab and installation) and one small issue with data > >> cleaning in boxplots. > >> > >> I proposing giving our selves a 2 week deadline to have everything > finalized. > >> > >> Tom > >> > > > > Excellent! Thanks very much for keeping on top of all this, and for the > > amazing amount of work you have been doing. > > I echo Eric's comments. > > Fantastic job, Thomas. > And very much appreciated! N > > -- > Damon McDougall > http://www.damon-is-a-geek.com > Institute for Computational Engineering Sciences > 201 E. 24th St. > Stop C0200 > The University of Texas at Austin > Austin, TX 78712-1229 > > > -- > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck® > Code Sight™ - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck® Code Sight™ - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] plot_directive, context and multiple plots
Hi, I am happily using `plot_directive`, but I've run into an inconvenience when using the 'context' option. Consider this rst file: ``` ### A title ### .. plot:: :context: import matplotlib.pyplot as plt plt.plot(range(10)) Then some text. .. plot:: :context: plt.figure() plt.plot(range(5), 'r') ``` In the second panel you see plots for both the first figure and the second figure, because the underlying code is making this call: fig_managers = _pylab_helpers.Gcf.get_all_fig_managers() to find all current figures, finding the first and the second figure, and rendering both. I think this is unlikely to be what the user expects (it confused me), but I wasn't sure what the best way to work round it was. I considered adding another option like `:myfigs: true` to the directive which would only pick up figures I create using the current code block - is there a better way? Cheers, Matthew -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] plot_directive, context and multiple plots
Wouldn't a better default be to just close all figures when they're displayed? It can't be common that someone wants to show the same plot repeatedly (and if they do that could have an option)...? -n On 14 Jul 2014 22:16, "Matthew Brett" wrote: > Hi, > > I am happily using `plot_directive`, but I've run into an > inconvenience when using the 'context' option. Consider this rst > file: > > ``` > ### > A title > ### > > .. plot:: > :context: > > import matplotlib.pyplot as plt > plt.plot(range(10)) > > Then some text. > > .. plot:: > :context: > > plt.figure() > plt.plot(range(5), 'r') > ``` > > In the second panel you see plots for both the first figure and the > second figure, because the underlying code is making this call: > > fig_managers = _pylab_helpers.Gcf.get_all_fig_managers() > > to find all current figures, finding the first and the second figure, > and rendering both. I think this is unlikely to be what the user > expects (it confused me), but I wasn't sure what the best way to work > round it was. I considered adding another option like `:myfigs: true` > to the directive which would only pick up figures I create using the > current code block - is there a better way? > > Cheers, > > Matthew > > > -- > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
