Improved datetime handling in utils to avoid type mixing #3530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I came across two util functions that do not take into account the possibility that different datetime types may be present in an array, such as when comparing axis ranges in overlayed plots (how this can happen in the first place might be worth investigating in more detail at some point). E.g. combining both pandas and numpy datetimes in the same array ruins calls such as to
numpy.max
etc.Fixes #3528