Skip to content

Backport PR #16906 on branch v3.2.1-doc (update FAQ on how to register pandas converters) #16928

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 27, 2020
+5 −13
Merged

Backport PR #16906 on branch v3.2.1-doc (update FAQ on how to register pandas converters) #16928

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 5 additions & 13 deletions doc/faq/howto_faq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,20 +21,12 @@ Plot `numpy.datetime64` values
As of Matplotlib 2.2, `numpy.datetime64` objects are handled the same way
as `datetime.datetime` objects.

If you prefer the pandas converters and locators, you can register their
converter with the `matplotlib.units` module::

from pandas.tseries import converter as pdtc
pdtc.register()

If you only want to use the `pandas` converter for `numpy.datetime64` values ::

from pandas.tseries import converter as pdtc
import matplotlib.units as munits
import numpy as np

munits.registry[np.datetime64] = pdtc.DatetimeConverter()
If you prefer the pandas converters and locators, you can register them. This
is done automatically when calling a pandas plot function and may be
unnecessary when using pandas instead of Matplotlib directly. ::

from pandas.plotting import register_matplotlib_converters
register_matplotlib_converters()


.. _howto-figure-empty:
Expand Down