Skip to content

DOC: Update timestamp limitations #52204

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

Merged
merged 2 commits into from
Mar 28, 2023
Merged
Changes from all commits
Commits
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
6 changes: 5 additions & 1 deletion doc/source/user_guide/timeseries.rst
Original file line number Diff line number Diff line change
Expand Up @@ -507,14 +507,18 @@ used if a custom frequency string is passed.
Timestamp limitations
---------------------

Since pandas represents timestamps in nanosecond resolution, the time span that
The limits of timestamp representation depend on the chosen resolution. For
nanosecond resolution, the time span that
can be represented using a 64-bit integer is limited to approximately 584 years:

.. ipython:: python
pd.Timestamp.min
pd.Timestamp.max
When choosing second-resolution, the available range grows to ``+/- 2.9e11 years``.
Copy link
Member

Choose a reason for hiding this comment

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

should we add a sentence about converting between these with as_unit?

Different resolutions can be converted to each other through ``as_unit``.

.. seealso::

:ref:`timeseries.oob`
Expand Down