Skip to content

Make sure Locators always return a tick out of bounds#25225

Closed
dstansby wants to merge 2 commits into
matplotlib:mainfrom
dstansby:autolocator-hypothesis
Closed

Make sure Locators always return a tick out of bounds#25225
dstansby wants to merge 2 commits into
matplotlib:mainfrom
dstansby:autolocator-hypothesis

Conversation

@dstansby

Copy link
Copy Markdown
Member

PR Summary

As part of discussing whether to merge #25173, I thought it was worth drafting the changes that would be needed to make our current locators respect returning at least one tick out of bounds.

I still need to investigate:

PR Checklist

Documentation and Tests

  • Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • New plotting related features are documented with examples.

Release Notes

  • New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

@dstansby dstansby changed the title Make MaxNLocator always return a tick out of bounds Make sure Locators always return a tick out of bounds Feb 15, 2023
@dstansby

Copy link
Copy Markdown
Member Author

This messes up histogram limits (among other things), so I'll close it. I've suggested a way forward for the docs at #25146 (comment)

hist_density

@dstansby dstansby closed this Feb 15, 2023
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.

1 participant