-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Revert #23417 (Consistently set label on axis with units) #25278
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
Conversation
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.
Happy to revert (sorry for breaking!), but I think at the same time we should put in a test that breaks before this PR was reverted, and passes afterwards, so we don't accidentally break things in the future.
7e1cf67
to
d0b5756
Compare
Don't have time to review the test now, but I'll remove my change request, thanks for adding a test!
Test added, it is a little bit apocryphal, as I don't really expect such things to be done with built in converters, but rather than introducing test-only subclasses, it still gets at the mechanism that I think is at the heart of the issue in #25219, that if a valid converter is applied to an |
…et label on axis with units)
PR Summary
PR #23417 caused problems for downstream libraries which provide unit converters.
The most prominent example is pandas, as discussed in depth in #25219 (edit: fixed linked discussion issue).
While there are other solutions that solve the narrow case, it was determined there that the pragmatic answer was to revert and sort out the details as a follow up.
PR Checklist
Documentation and Tests
pytest
passes)Release Notes
.. versionadded::
directive in the docstring and documented indoc/users/next_whats_new/
.. versionchanged::
directive in the docstring and documented indoc/api/next_api_changes/
next_whats_new/README.rst
ornext_api_changes/README.rst