Skip to content
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

Make Axes.semilogx and semilogy consistent in handling negative coords #11193

Closed
Zac-HD opened this issue May 8, 2018 · 1 comment
Closed
Labels
status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action topic: axes

Comments

@Zac-HD
Copy link
Contributor

Zac-HD commented May 8, 2018

Axes.semilogy has different default behaviour for out-of-bounds coords than Axes.semilogx - the former clips them to 0+eps, while in the x-dimension they're masked. The latter is thought to be the correct behavior. IIRC Axes.loglog is also affected.

However, if you trace back to matplotlib.scale.LogScale, the defaults there are both 'clip'.

This issue was discovered while working on #11137, so it would be nice to make the signatures involved more explicit at the same time as making the behavior consistent.

@github-actions
Copy link

github-actions bot commented Jun 5, 2023

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!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Jun 5, 2023
@github-actions github-actions bot added the status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. label Jul 5, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action topic: axes
Projects
None yet
Development

No branches or pull requests

2 participants