-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
MNT: simplify AutoDateFormatter #11770
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
Conversation
- import constants from matplolib.dates - do not re-implement AutoDateFormatter functionality that is already upstream
can you show an example of where this was doing the wrong thing? (e.g. a test for this) |
There is nothing wrong, it just was an almost copy-paste job from mpl to pandas. This change should have 0 functional change. |
ok, seems like we were just overriding mpl code. Since everything passed, this either was never tested (probably), or works ok :) |
MNT: simplify AutoDateFormatter
30.: '%b %Y', | ||
1.0: '%b %d %Y', | ||
1. / 24.: '%H:%M:%S', | ||
1. / 24. / 3600. / 1000.: '%H:%M:%S.%f' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found the difference between what was here and what is in MPL it is the extra 1000 in the last entry.
I will have a PR shortly.
Reverts part of: pandas-dev#11770 Closes: matplotlib/matplotlib#6365 The mistake in pandas-dev#11770 was missing that pandas had a 1/us not 1/s scaled bucket.
revert part of #11770 xref: matplotlib/matplotlib#6365 closes #13131 The mistake in #11770 was missing that pandas had a 1/us not 1/s scaled bucket.
is already upstream