Ok, my brain hurts... why is it that v1.5.3 has a different behavior from
master?

Sorry for prematurely closing this issue. It appears we got ourselves into
a little bind in our efforts to remove hard-coded defaults and defer to the
rcParams whenever an argument is None. We must have not appreciated that
None actually had sematic value for certain things.

My vote at this point is to start a (long) deprecation process for None as
a marker value, given how ingrained it seems to be.

On Tue, Oct 4, 2016 at 3:11 PM, Eric Firing notifications@github.com
wrote:

There is nothing we can do about it for the 1.5 series. A quick check
indicates that v2.x and master behave like the earlier versions, not like
1.5.3. The remaining question is whether any deprecations, changes in
documentation, or additional tests are needed for v2.x and master.

My opinion is that the None object should not be listed in that
documentation table as being equivalent to the 'none' string, even though
it has the same effect in practice.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7218 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARy-BXrFoscTLTbS3kI-vL-l_E1LIP9ks5qwqTUgaJpZM4KN-7L
.

Uh oh!

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions