Fix conflict with matplotlib #29
Open
Conversation
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
Contributor
|
Would solve (and close) #30. Would the versions of matplotlib specified in |
…nd Connected Double Nulls.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of changes
//: After downloading, there was a version conflict when using the newer version of matplotlib. Fixed the conflict according to the matplotlib documentation.# (Add a quick note on what this PR intends to accomplish.)
How was this tested?
//: By running the tests in the tutorial in the docs for the single null configuration. (it failed before when trying to create the patch map and now it works).# (Add a quick note on how this was tested.)
Relevant issues
Checklist