8000 Backport PR #22283: Fixed `repr` for `SecondaryAxis` by oscargus · Pull Request #22325 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

Backport PR #22283: Fixed repr for SecondaryAxis #22325

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

Merged

Conversation

oscargus
Copy link
Member

PR Summary

Manual cherry-picking as the original attempt to back-port had conflicts.

(I included all the additional tests as well as I am not sure if you merge 3.5.x and main at some stage or not and no harm having them there anyway,)

PR Checklist

Tests and Styling

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (install flake8-docstrings and run flake8 --docstring-convention=all).

Documentation

  • New features are documented, with examples if plot related.
  • New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).

@oscargus oscargus changed the title Backport PR #22283: Fixed repr for `SecondaryAxis Backport PR #22283: Fixed repr for SecondaryAxis Jan 26, 2022
@oscargus oscargus force-pushed the auto-backport-of-pr-22283-on-v3.5.x branch from ccd0f1b to 44a4c52 Compare January 26, 2022 18:12
@tacaswell
Copy link
Member

The 3.5.x branch will get merged up every so often, typically right after we do a release so that git describe gives the right answer.

Cherry-picking back any tests adding with the change is the right thing to do so we are sure that the backport also actually fixes the bug. Because we do not backport everything it is possible that the fix on the main branch implicitly relies on some other non-backported change to function properly.

@tacaswell tacaswell added this to the v3.5.2 milestone Jan 26, 2022
@oscargus
Copy link
Member Author

tests adding with the change is the right thing to do

Yes, indeed the test for the change. Here I also added a bunch of other tests to get coverage up, so those were the ones I primarily referred to. But no harm adding those anyway.

@tacaswell
Copy link
Member

Oh, I understand now. Backporting all of the tests you added in that PR is the right thing to do 👍🏻

@QuLogic QuLogic closed this Jan 26, 2022
@QuLogic QuLogic reopened this Jan 26, 2022
@QuLogic QuLogic merged commit ffb11cd into matplotlib:v3.5.x Jan 27, 2022
@oscargus oscargus deleted the auto-backport-of-pr-22283-on-v3.5.x branch January 27, 2022 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0