handle deprecation of pandas.Series.dt.to_pydatetime() calls and suppress their FutureWarnings #4379
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.
As of Pandas 2.1.0, it is deprecating the behaviour of
Series.dt.to_pydatetime()
, which currently returns anumpy.ndarray
, and changing it to return apandas.Series
of Python datetime objects.https://pandas.pydata.org/docs/reference/api/pandas.Series.dt.to_pydatetime.html
This PR fixes #4363. The issue is that user's consoles are currently spammed with a
FutureWarning
containing this warning, which they cannot do anything about as the warning is coming inside the Plotly Package.The fix is to first wrap the output of
Series.dt.to_pydatetime()
with annp.array()
call, so that the code will continue to work when the behaviour change drops. Then secondly, each offending call is put inside awarnings.catch_warnings()
context manager that suppresses theFutureWarning
only for the contents of thewith
block.Code PR
plotly.graph_objects
, my modifications concern thecodegen
files and not generated files.modified existing tests.
new tutorial notebook (please see the doc checklist as well).