Re: [matplotlib-devel] pyplot functions: do you rely on the "hold" kwarg?

2015-06-07 Thread Eric Firing
On 2015/06/07 12:05 PM, Nathaniel Smith wrote: > On Sun, Jun 7, 2015 at 2:37 PM, Eric Firing wrote: >> Matplotlib's pyplot retains quite a few vestiges from its original >> Matlab-workalike heritage; we would like to gradually eliminate those >> that no longer make sense. One such candidate is th

Re: [matplotlib-devel] pyplot functions: do you rely on the "hold" kwarg?

2015-06-07 Thread Nathaniel Smith
On Sun, Jun 7, 2015 at 2:37 PM, Eric Firing wrote: > Matplotlib's pyplot retains quite a few vestiges from its original > Matlab-workalike heritage; we would like to gradually eliminate those > that no longer make sense. One such candidate is the "hold" kwarg that > every pyplot function has, wit

[matplotlib-devel] pyplot functions: do you rely on the "hold" kwarg?

2015-06-07 Thread Eric Firing
Matplotlib's pyplot retains quite a few vestiges from its original Matlab-workalike heritage; we would like to gradually eliminate those that no longer make sense. One such candidate is the "hold" kwarg that every pyplot function has, with a "True" default. I don't think it serves any useful