Skip to content

DOC: add note about the values of unit for pd.to_datetime #34899

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 2 commits into from
Jun 20, 2020
Merged

DOC: add note about the values of unit for pd.to_datetime #34899

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d144a5e
DOC: add note about the values of unit for pd.to_datetime
AidanMontare Jun 20, 2020
5e8ab3c
DOC: clarified note on units argument
AidanMontare Jun 20, 2020
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
5 changes: 5 additions & 0 deletions doc/source/user_guide/timeseries.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,6 +319,11 @@ which can be specified. These are computed from the starting point specified by
pd.to_datetime([1349720105100, 1349720105200, 1349720105300,
1349720105400, 1349720105500], unit='ms')

.. note::

The strings used to specify a ``unit`` are not the same are those by ``format``.
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not really sure what format refers to here, can you clarify

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure! I'm talking about the "%Y-%M-%D" -type strings. Is the new commit clearer?

The available units are listed on the documentation for :func:`pandas.to_datetime`.

Constructing a :class:`Timestamp` or :class:`DatetimeIndex` with an epoch timestamp
with the ``tz`` argument specified will currently localize the epoch timestamps to UTC
first then convert the result to the specified time zone. However, this behavior
Expand Down