Compatibility with vedo 2023.5.0#43
Merged
alessandrofelder merged 1 commit intobrainglobe:masterfrom Nov 16, 2023
Merged
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
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.
Before submitting a pull request (PR), please read the contributing guide.
Description
What is this PR
Makes the code compatible with vedo 2023.5.0.
Why is this PR needed?
vedo 2023.5.0 released yesterday.
What does this PR do?
Changes an import statement and pins vedo>=2023.5.0 as this is a breaking change.
References
closes #42
How has this PR been tested?
Code has been tested locally.
Is this a breaking change?
Yes, users will have to update to vedo 2023.5.0 since
vedo.colors.py::colorMapis nowvedo.colors.py::color_mapDoes this PR require an update to the documentation?
No
Checklist: