You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because Spine is mostly written for rectilinear axes, calling some seemingly harmless methods on polar spines can completely mess up their positioning.
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug summary
Because Spine is mostly written for rectilinear axes, calling some seemingly harmless methods on polar spines can completely mess up their positioning.
Code for reproduction
or
Actual outcome
Expected outcome
The spine stays correct, or at least the get_foo getter raises an exception.
Matplotlib version
print(matplotlib.get_backend())
): qt5aggThe text was updated successfully, but these errors were encountered: