I'd like to propose an update to the default boxplot symbology: all black
Q: How much more black could the boxplots be?
A: None. None more black.
(sorry, ben)
On Fri, Nov 21, 2014 at 7:18 PM, Benjamin Root wrote:
> With regards to defaults for 2.0, I am actually all for breaking them for
> the
On 2014/11/23, 12:18 PM, Benjamin Root wrote:
> Reading through the backend_wx.py code, I noticed a small deviation from
> the other interactive backends. All other
> new_figure_manager_given_figure() separately creates a canvas and
> manager object (which, in turn, creates the window object) and h
Reading through the backend_wx.py code, I noticed a small deviation from
the other interactive backends. All other new_figure_manager_given_figure()
separately creates a canvas and manager object (which, in turn, creates the
window object) and hooks them all up. The manager would handle all window
On 2014/11/22, 7:43 PM, Benjamin Root wrote:
> I don't have a mac to double-check, but reading through the
> backend_cocoaagg.py, I don't see any creation of a navigation toolbar?
> Is this assumption right?
Probably so:
from matplotlib import cbook
cbook.warn_deprecated(
'1.3',
message
On 2014/11/22, 9:06 AM, gary ruben wrote:
> A few thoughts to add to the excellent ones to date, to do with colorbar
> behaviour.
> My general comment would be that if the axis tick formatter defaults are
> changed not to forget about the colorbar as I typically find it needs
> more tweaking than t
