Repository navigation
Fix errorbar zorder v1.2 - #1628
Merged
Merged
Conversation
Member
Author
|
The 3.1 build failed with errors that look like Travis didn't actually use 3.1 to run the tests. |
ghost
assigned
Member
|
@tacaswell Thanks for the patch. I'll leave this up for a day or so to allow the opinions of others to roll in before merging. |
Member
|
A related issue: #409 |
Member
|
@WeatherGod Does this patch fix that issue for you? |
Member
|
I have yet to check, I was merely noting it for posterity. I have a huge backlog of emails to work through today... |
Do not need to explicitly call set_zorder because it gets done in the call to coll.update.
Member
|
+1 |
Member
There was a problem hiding this comment.
PEP8: A space is needed after each comma in the above calls to ax[vh]line.
Member
|
Once those nitpicks are addressed I'll merge this. Thanks @tacaswell. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix for issue #1622 + unit test.