Skip to content

BUG: Raise when casting NaT to int #28492

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 18 commits into from
Jan 1, 2020
Merged

BUG: Raise when casting NaT to int #28492

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
0c035bc
BUG: Raise when casting NaT to int
Sep 17, 2019
0d64522
Add release note
Sep 18, 2019
3d91a8f
Add PR number
Sep 18, 2019
482d629
Use isna
Sep 18, 2019
975de26
Parametrize test
Sep 18, 2019
3445dc7
Check all integer dtypes
Sep 18, 2019
2e9ece9
Merge branch 'master' into cast-nat
Sep 18, 2019
e23b9a0
Fix merge
Sep 18, 2019
b14d752
Edit release note
Sep 18, 2019
9419744
Check for np.int64
Sep 19, 2019
b81f433
Handle timedelta64
Sep 19, 2019
e5dfa71
Merge branch 'master' into cast-nat
Sep 20, 2019
18734ff
Add astype_nansafe datetime tests
Sep 19, 2019
c9ba768
Add test for NaT object casting
Sep 25, 2019
5da8246
Merge branch 'master' into cast-nat
Nov 8, 2019
ac501f6
Merge branch 'master' into cast-nat
Nov 20, 2019
e229844
Merge branch 'master' into cast-nat
Nov 21, 2019
931e8c5
Merge branch 'master' into cast-nat
Dec 30, 2019
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
1 change: 1 addition & 0 deletions doc/source/whatsnew/v1.0.0.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,7 @@ Datetimelike
- Bug in :class:`Timestamp` subtraction when subtracting a :class:`Timestamp` from a ``np.datetime64`` object incorrectly raising ``TypeError`` (:issue:`28286`)
- Addition and subtraction of integer or integer-dtype arrays with :class:`Timestamp` will now raise ``NullFrequencyError`` instead of ``ValueError`` (:issue:`28268`)
- Bug in :class:`Series` and :class:`DataFrame` with integer dtype failing to raise ``TypeError`` when adding or subtracting a ``np.datetime64`` object (:issue:`28080`)
- Bug in :meth:`Series.astype` failing to handle ``pd.NaT`` when casting to an integer dtype (:issue:`28492`)
-


Expand Down
4 changes: 4 additions & 0 deletions pandas/core/dtypes/cast.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@
from pandas._libs.tslibs import NaT, OutOfBoundsDatetime, Period, iNaT
from pandas.util._validators import validate_bool_kwarg

import pandas as pd

from .common import (
_INT64_DTYPE,
_NS_DTYPE,
Expand Down Expand Up @@ -696,6 +698,8 @@ def astype_nansafe(arr, dtype, copy=True, skipna=False):
if is_object_dtype(dtype):
return tslib.ints_to_pydatetime(arr.view(np.int64))
elif dtype == np.int64:
Copy link
Contributor

Choose a reason for hiding this comment

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

this likely needs to be is_integer_dtype(dtype)

Copy link
Member Author

@dsaxton dsaxton Sep 19, 2019 •
edited
Loading

Choose a reason for hiding this comment

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

I think this might actually need to be np.int64 since above we check for datetime64 (getting some weird test failures after this change). Looking at the numpy documentation it seems the output of view is "unpredictable" when the precision differs between the data types (the shape of the output can even change).

if pd.isnull(arr).any():
raise ValueError("Cannot convert NaT values to integer")
return arr.view(dtype)

# allow frequency conversions
Expand Down
9 changes: 9 additions & 0 deletions pandas/tests/dtypes/test_common.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@

import pandas.util._test_decorators as td

from pandas.core.dtypes.cast import astype_nansafe
import pandas.core.dtypes.common as com
from pandas.core.dtypes.dtypes import (
CategoricalDtype,
Expand Down Expand Up @@ -731,3 +732,11 @@ def test__is_dtype_type_sparse():
result = np.dtype("int32")
assert com._is_dtype_type(ser, lambda tipo: tipo == result)
assert com._is_dtype_type(ser.dtype, lambda tipo: tipo == result)


def test__nansafe_nat_to_int():
Copy link
Contributor

Choose a reason for hiding this comment

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

rename to

test_astype_nansafe; can you parameterize this on all ints at the very least. ideally we would have more testing for this (but can be followup)

Copy link
Member Author

Choose a reason for hiding this comment

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

For the other (non-int64) dtypes we end up hitting the TypeError here (related to the above comment):

pandas/pandas/core/dtypes/cast.py

Line 707 in b81f433

raise TypeError(

Would you recommend breaking these out into a separate test?

arr = np.array([np.datetime64("NaT")])

msg = "Cannot convert NaT values to integer"
with pytest.raises(ValueError, match=msg):
astype_nansafe(arr, dtype=np.int64)