-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
FIX: undeprecate and update num2epoch/epoch2num #17983
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
Marking as release critical - this will break anyone using pandas date converter and Matplotlib 3.0. |
Do we need to pull back notes in API changes too? |
Probably, unless we wanted to soft un-deprecate it 😉 I don't think we should be maintaining a second floating-point date representation. Looking at pandas, I think they don't need the call any more either since we have supported datetime64 for quite while.... |
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.
Blocking on updating API change note.
1487765
to
52528fe
Compare
52528fe
to
32ef145
Compare
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
OK, this is upset because 3.3.x is not tracking |
In the past we have added sections to the top of the minor version API changes page for the patch-release back-tracking on the deprecation (or had to retro-actively document accidentally API changes). |
…epoch FIX: undeprecate and update num2epoch/epoch2num
PR Summary
#15008 added a new variable epoch.
At the time I did not update the unfortunately named
epoch2num
andnum2epoch
because Matplotlib does not use these. They are also ill-named because in this caseepoch
refers to a UNIX-like time of seconds since 1970-01-01, and thats not at all what an epoch is. We also deprecated these functions at the time.Unfortunately pandas uses them, and they need to be made compatible with the new epoch handling. pandas-dev/pandas#35350 and pandas-dev/pandas#34850
Here I've updated those functions to work with the variable epoch, and removed the deprecation, and added a test for the basic functionality with both the old and new epoch.
On the pandas side,
is fixed, with no further work on their side needed.
PR Checklist