is_timedelta64_object behaves differently on older versions?

Author: patrickmckenna

pandas/_libs/tslibs/timedeltas.pyx

@@ -907,7 +907,9 @@ cdef object create_timedelta(object value, str in_unit, NPY_DATETIMEUNIT out_res
             if util.is_nan(value):
                 return NaT
             out_value = <int64_t>value
-        elif is_timedelta64_object(value):
+        # is_timedelta_64_object may not give correct results w/ some versions?
+        # see e.g. https://github.com/pandas-dev/pandas/runs/6397652653?check_suite_focus=true#step:11:435
+        elif isinstance(value, np.timedelta64):
             out_value = ensure_td64ns(value).view(np.int64)
         elif isinstance(value, str):
             if value.startswith(("P", "-P")):

pandas/tests/scalar/timedelta/test_constructors.py

@@ -225,16 +225,15 @@ def test_overflow_on_construction(td_overflow_msg: str):
         (9223372037, "s", " seconds"),  # 44 seconds
     ],
 )
-def test_construction_out_of_bounds_td64(val, unit, name):
+def test_construction_out_of_bounds_td64(val, unit, name, td_overflow_msg: str):
     # TODO: parametrize over units just above/below the implementation bounds
     #  once GH#38964 is resolved
 
     # Timedelta.max is just under 106752 days
     td64 = np.timedelta64(val, unit)
     assert td64.astype("m8[ns]").view("i8") < 0  # i.e. naive astype will be wrong
 
-    msg = str(val) + name
-    with pytest.raises(OutOfBoundsTimedelta, match=msg):
+    with pytest.raises(OutOfBoundsTimedelta, match=td_overflow_msg):
         Timedelta(td64)
 
     # But just back in bounds and we are OK
@@ -243,7 +242,7 @@ def test_construction_out_of_bounds_td64(val, unit, name):
     td64 *= -1
     assert td64.astype("m8[ns]").view("i8") > 0  # i.e. naive astype will be wrong
 
-    with pytest.raises(OutOfBoundsTimedelta, match="-" + msg):
+    with pytest.raises(OutOfBoundsTimedelta, match=td_overflow_msg):
         Timedelta(td64)
 
     # But just back in bounds and we are OK