Fix for Ginga upstream deprecation #236
Merged
Conversation
This file contains 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
- the move_to(x, y) call on a canvas object has been redefined in terms of move_to_pt((x, y)) since Ginga v2.6.5. move_to() has issued a DeprecationWarning since v4.0.0 - this fixes the plugins to use move_to_pt(). It is compatible with Ginga back to v2.6.5
|
🙇♂️ |
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.
Description
Address upstream deprecation of the move_to() call on a Ginga canvas object
the move_to(x, y) call on a canvas object has been redefined in terms of move_to_pt((x, y)) since Ginga v2.6.5. move_to() has issued a DeprecationWarning since v4.0.0
this fixes the plugins to use move_to_pt(). It is compatible with Ginga back to v2.6.5