Timestamp.resolution returns timedelta(microseconds=1)

[jbrockmendel]

I hadn't even noticed that resolution was a datetime property until now, but it returns timedelta(0, 0, 1). Timestamp doesn't override that. I expect the correct thing to do is to return Timedelta(nanoseconds=1). Pretty low priority.

[gfyoung]

Pretty low priority.

@jbrockmendel : How easy would it be to patch?

[jbrockmendel]

super-duper easy. Might merit a "Good First Issue" tag.

[gfyoung]

Might merit a "Good First Issue" tag.

Then let's label as such. Done.

[uds5501]

@jbrockmendel @gfyoung Any guidance for the patch of the same?

[jbrockmendel]

You'll want to define a property on the Timestamp class that just returns Timedelta(nanoseconds=1). For the sake of thoroughness you'll need a super-simple test in pandas.tests.scalar.timestamp.test_timestamp.

[drewmassey]

So I'm looking at

pandas/pandas/_libs/tslibs/timedeltas.pyx

Line 797 in 9d61ab5

def resolution(self):

and I think fixing this would be breaking change ... it isn't hard to change the return values but is that really the desired behavior?

[mroeschke]

@drewmassey your snippet is looking at timedeltas.pyx (which has a relevant resolution issue open #21344). This issue would entail adding a resolution property to timestamp.pyx