Thanks to visit codestin.com
Credit goes to github.com

Skip to content

do not cause warning in seaborn #13623

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.

Sign up for GitHub

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

Jump to bottom
Closed
tacaswell opened this issue Mar 8, 2019 · 0 comments · Fixed by #13631
Closed

do not cause warning in seaborn #13623

tacaswell opened this issue Mar 8, 2019 · 0 comments · Fixed by #13631
Labels
Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Milestone
v3.1.0

Comments

@tacaswell
Copy link
Member

I mean it used to be a simple alias, self.label = self.label1. So that shouldn't be a problem. I just wanted to make sure we are aware of the implication that once 3.1 is released thousands of seaborn users will get some warning message.

Originally posted by @ImportanceOfBeingErnest in #10088 (comment)
@tacaswell tacaswell added this to the v3.1.0 milestone Mar 8, 2019
@tacaswell tacaswell added the Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. label Mar 8, 2019
@anntzer anntzer mentioned this issue Mar 8, 2019
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
Projects
None yet
Milestone
v3.1.0
Development

Successfully merging a pull request may close this issue.

Switch deprecation of Tick.label to pending. anntzer/matplotlib
1 participant
@tacaswell