Skip to content

partial fix for issue #7712 #8251

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
wants to merge 1 commit into from

Conversation

ParagBh
Copy link

@ParagBh ParagBh commented Mar 10, 2017

Partial fix for issue #7712 where text was overlapping due to too many ticks so I reduced the default number of ticks which takes care of the overlapping issue. Also added an automated testcase under test_dates.py. I have also never contributed ever to an open source project so if I did something wrong please let me know.

@tacaswell tacaswell added this to the 2.1 (next point release) milestone Mar 10, 2017
@tacaswell tacaswell modified the milestones: 2.0.1 (next bug fix release), 2.1 (next point release) Mar 10, 2017
@tacaswell
Copy link
Member

This is an API change (as the output images for identical input changes), but that does not immediately rule it out. If we do make this change it will need an entry in https://github.com/matplotlib/matplotlib/tree/master/doc/api/api_changes

We apparently have some tests that exercise this code path 😺 . We either need to re-generate those tests or make this an rcparam we can patch over in the tests.

How did you pick these numbers?

Tagged a 2.0.1 as it is a style change and we are already planning to ship a number of other small style changes for 2.0.1.

@ParagBh
Copy link
Author

ParagBh commented Mar 10, 2017

@tacaswell

When playing around for the numbers for DAILY, I realized that the datetime values start overlapping when there are 7 or more ticks so I simply reduced it to 6. I did something similar for MONTHLY.

@QuLogic QuLogic modified the milestones: 2.0.1 (next bug fix release), 2.0.2 (next bug fix release) May 3, 2017
@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.0.3 (next bug fix release) Jul 10, 2017
@tacaswell
Copy link
Member

@ParagBh Are you still interested in working on this?

I am nominally 👍 on this, but a number of the existing tests will need to be updated.

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Aug 29, 2017
@jklymak
Copy link
Member

jklymak commented Jul 25, 2019

I think some of this is probably obsolete at this point, but feel free to re-open if I'm mistaken. Thanks a lot for the PR!

@jklymak jklymak closed this Jul 25, 2019
@story645 story645 removed this from the future releases milestone Oct 6, 2022
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.

5 participants