-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: Display deprecated warnings for mapbox traces #4900
Merged
+88
−0
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
aba3ab2
display deprecated warnings for mapbox traces and skip their validati…
archmoj 4010260
add DeprecationWarning warning type in codegen
emilykl c187794
capitalization
emilykl cb3dba7
clean up basedatatypes (return to previous)
emilykl 9908d72
add deprecation warnings to px mapbox functions
emilykl 3b31f3a
formatting
emilykl e688d28
Merge branch 'master' into v6-mapbox-deprecated-warning
emilykl 5d113b9
cleanup
emilykl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@emilykl Good improvement. And I can approve this PR.
As follow ups to this PR:
Could you possibly
stacklevel=2
is the best option we could use?stacklevel
andcategory
options for other warnings in plotly.py?Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe
stacklevel=2
is the correct option in this case -- it causes the warning to appear to be emitted at the place in the user's code where they have called the deprecated function, for example:(Also, for
DeprecationWarning
specifically, using any otherstacklevel
for these deprecations causes the warning to not appear at all.)It's just coincidence that
stacklevel=2
is the correct option in this case for both thego
andpx
deprecations... the correct stacklevel will differ in every case depending on exactly where the warning is being emitted.I don't think it's worth the effort to go through the codebase and clean up existing warnings, but I do think it makes sense to use
stacklevel
andcategory
consistently going forward. It seems at least some of the warnings already in place in Plotly.py are using them correctly.