Skip to content

fix and test deprecated layout method toggling #22849

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

Closed

Conversation

richardsheridan
Copy link
Contributor

PR Summary

Fixes #22847. Not sure if there are knock-on effects, looking forward to code review.

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).

@richardsheridan richardsheridan requested a review from jklymak April 14, 2022 18:43
@jklymak
Copy link
Member

jklymak commented Apr 14, 2022

Just a heads up that I cannot review anything properly for a week or so. Thanks!

@QuLogic QuLogic added this to the v3.6.0 milestone Apr 15, 2022
@greglucas
Copy link
Contributor

Is None the "null"-layout engine? It looks like there is also mention of the string "none" here:
#22452
So, I'm curious if this is currently allowed, or if that PR needs to go in first?

@jklymak jklymak marked this pull request as draft June 30, 2022 08:45
@richardsheridan
Copy link
Contributor Author

Any interest in doing this for 3.5.3 and saving #22452 for 3.6.0?

@tacaswell
Copy link
Member

Sorry, I missed this entirely until I saw it was closed! In the future, please err on the side of re-milestoning things back if you want them to be in a bug fix release.

The reason #22452 picked up all of the extra complexity is that just setting it back to None could end up breaking the colorbars so I would still be wary of this fix.

@QuLogic QuLogic modified the milestones: v3.6.0, unassigned Sep 9, 2022
QuLogic added a commit to QuLogic/matplotlib that referenced this pull request Jan 10, 2023
Re-uses the tests from matplotlib#22849, but also tests that going _back_ on works
as well.

Fixes matplotlib#22847

Co-authored-by: richardsheridan <richard.sheridan@gmail.com>
QuLogic added a commit to QuLogic/matplotlib that referenced this pull request Jan 10, 2023
Re-uses the tests from matplotlib#22849, but also tests that going _back_ on works
as well.

Fixes matplotlib#22847

Co-authored-by: richardsheridan <richard.sheridan@gmail.com>
@QuLogic QuLogic mentioned this pull request Jan 10, 2023
1 task
@richardsheridan richardsheridan deleted the toggle_layout branch March 31, 2023 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Cannot toggle set_tight_layout
6 participants