Fix issues we encountered in matplotlib 3.10 #1833
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
This will also unpin the matplotlib version as a result. I did not immediately see any further issues, but if we encounter more in the future, we can hopefully fix them quickly. Thanks @patquem for the pointer in #1772! Signed-off-by: Patrick Avery <[email protected]>
psavery
force-pushed
the
fix-matplotlib-3.10
branch
from
a6c50bb to
a757668
Compare
Collaborator
Author
|
@saransh13 @bnmajor Can either of you review? You will need to upgrade matplotlib on your computer. If we run into more issues, hopefully we can fix them pretty quickly. The changes matplotlib make did result in errors in numerous places. |
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.
This will also unpin the matplotlib version as a result.
I did not immediately see any further issues, but if we encounter more in the future, we can hopefully fix them quickly.
Thanks @patquem for the pointer in #1772!
Fixes: #1772