Even though I'm familiar with the boxplot source code, I largely use IPython for quick investigations like this.
In IPython, doing something like "matplotlib.Axes.boxplot??" shows the full source code for that functions\. Then I saw/remembered that boxplot now just calls matplotlib.cbook.boxplot_stats and passes the results to matplotlib.Axes.bxp. So then I did "matplotlib.cbook.boxplot_stats" to see how the whiskers were computed. -paul On Wed, Aug 26, 2015 at 8:43 PM, chtan <ch...@unisim.edu.sg> wrote: > Uh, now I understand why it's behaving this way. Tx Paul. > > >From the documentation, it seems natural to expect the behaviour to be > uniform throughout the meaningful range for IQR. > > How may I go about searching for the responsible code on my own in > situations like this? > >From the perplexing behaviour to the little nugget in > matplotlib.cbook.boxplot_stats, the path isn't clear to me. > > Any general advice? > > > > -- > View this message in context: > http://matplotlib.1069221.n5.nabble.com/boxplot-behaviour-in-an-extreme-scenario-tp46027p46032.html > Sent from the matplotlib - users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
------------------------------------------------------------------------------
_______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
