fix #4854: set default numpoints of legend entries to 1 #5131

Merged
merged 2 commits into from Feb 8, 2016

Conversation

Projects
None yet
5 participants
Contributor

gauteh commented Sep 24, 2015

check #4854: set default numpoints to 1.

I am a bit unsure abouth wether classic.mplstyle should be changed.

Owner

jenshnielsen commented Sep 24, 2015

The classic style should have numpoints=2, The idea of the classic style is to provide a style that exactly replicates how MPL looked before the default changes.

Contributor

gauteh commented Sep 24, 2015

Also apparently the test-images must be updated when the PR is ready.

Owner

jenshnielsen commented Sep 24, 2015

No the tests run with the classic style as default to avoid having to update all the test images.

tacaswell added this to the next major release (2.0) milestone Sep 24, 2015

Owner

tacaswell commented Sep 24, 2015

Please don't merge this until we have pushed the 1.5 development off the master branch.

Member

WeatherGod commented Sep 24, 2015

Hmmm, that is strange that only the legend_expand tests failed. Could that codepath be utilizing rcparams incorrectly?

Member

QuLogic commented Dec 3, 2015

@gauteh Can you rebase? I believe something has corrected the failure on master.

gauteh added some commits Sep 24, 2015

@gauteh gauteh fix #4854: set default numpoints of legend entries to 1 0ebfc96
@gauteh gauteh classic style should not be changed
a636f58

@tacaswell tacaswell added a commit that referenced this pull request Feb 8, 2016

@tacaswell tacaswell Merge pull request #5131 from gauteh/numpoints-1
fix #4854: set default numpoints of legend entries to 1
d3a9782

@tacaswell tacaswell merged commit d3a9782 into matplotlib:master Feb 8, 2016

2 of 3 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 67.487%
Details
Member

QuLogic commented Oct 16, 2016

Backported as part of #5774.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment