On Tue, Jan 22, 2013 at 9:10 PM, Drain, Theodore R (343P) <
theodore.r.dr...@jpl.nasa.gov> wrote:
> I have to say I disagree with this "fix". None was a nice, very intuitive
> way to hide the label. Many Python systems use None in that kind of role
> and I really doubt anyone is going to use None when they meant "None" so
> converting it to a string seems like a bad idea.
>
> Ted
>
>
IIRC, the problem is that in matplotlib, the python None has a special
meaning in most places ("do the default thing"). Legends, by default, will
create default labels. For some time, we were capable of distinguishing
when someone submitted label=None and didn't state anything at all for
labels. This often causes confusion down the draw stack, and we have been
working towards getting rid of such distinctions.
Of course, this is all from memory, which is notoriously bad. If someone
else can bisect the commit that changed this, maybe that can refresh my
memory and maybe I could see a reason to re-instate this behavior. Also,
if anyone can spot where it is stated in the documentation or examples that
None acts the same as "_nolegend_", then we can consider this a regression
and get it fixed.
Cheers!
Ben Root
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
