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

FIX: revert part of #11770 #13131

Closed
wants to merge 1 commit into from
Closed

Conversation

tacaswell
Copy link
Contributor

Reverts part of:

#11770

Closes:

matplotlib/matplotlib#6365

The mistake in #11770 was missing that pandas had a 1/us not 1/s
scaled bucket.

@jorisvandenbossche jorisvandenbossche added Bug Datetime Datetime data dtype Visualization plotting labels May 11, 2016
@jorisvandenbossche jorisvandenbossche added this to the 0.18.2 milestone May 11, 2016
SEC_PER_DAY = SEC_PER_HOUR * HOURS_PER_DAY
SEC_PER_WEEK = SEC_PER_DAY * DAYS_PER_WEEK

MUSECONDS_PER_DAY = 1e6 * SEC_PER_DAY
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tacaswell Are all these constants needed? (in the original PR, it were only 4 that you removed)

@jreback
Copy link
Contributor

jreback commented May 11, 2016

@tacaswell any tests?

can you add a whatsnew note? (can be something as simple as compat for .....issue because of incorrect tick display with mpl < 2.0....)

@tacaswell tacaswell force-pushed the fix_autodate branch 2 times, most recently from c3d8f27 to d4df66b Compare May 12, 2016 02:03
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.
@tacaswell
Copy link
Contributor Author

Only took 4 force-pushes to get there.

@jorisvandenbossche Added back the minimal set of constants to compute what was needed.

What sort of test do you want for this? You merged the last one with out a test 👿

@jreback
Copy link
Contributor

jreback commented May 12, 2016

can u create something that failed on the previous and now works? just maybe a check on axis ticks or something simple

@jreback jreback closed this in 9d44e63 May 20, 2016
@jreback
Copy link
Contributor

jreback commented May 20, 2016

thanks @tacaswell pls verify with mpl >= 2.0 when you have a chance.

@jreback
Copy link
Contributor

jreback commented May 20, 2016

did we have an issue where this came up on pnadas side? or was only on mpl side?

@TomAugspurger @jorisvandenbossche

@TomAugspurger
Copy link
Contributor

Only on the MPL tracker.

@tacaswell
Copy link
Contributor Author

Sorry i took to long to get a test in.

On Fri, May 20, 2016, 10:37 Tom Augspurger notifications@github.com wrote:

Only on the MPL tracker.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#13131 (comment)

@jreback
Copy link
Contributor

jreback commented May 21, 2016

np

ideally if u can post a couple of assertions we can add something to prevente future regressions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Datetime Datetime data dtype Visualization plotting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants