Description
-
I have checked that this issue has not already been reported.
-
I have confirmed this bug exists on the latest version of pandas (1.0.3).
-
(optional) I have confirmed this bug exists on the master branch of pandas.
Code Sample, a copy-pastable example
>>> import pandas as pd
>>> pd.Timedelta(1 / 128, "seconds").resolution_string
'N'
>>> pd.Timedelta(seconds=1 / 128).resolution_string
'U'Problem description
The resolution of Timedelta differs when created with value and unit, versus with keyword arguments. When tested with seconds as units, the former will round to nanoseconds, while the latter rounds to microseconds.
Expected Output
They should both have the same resolution, nanoseconds making the most sense to me:
>>> pd.Timedelta(seconds=1 / 128).resolution_string
'N'Output of pd.show_versions()
INSTALLED VERSIONS
commit : None
python : 3.8.2.final.0
python-bits : 64
OS : Darwin
OS-release : 19.4.0
machine : x86_64
processor : i386
byteorder : little
LC_ALL : None
LANG : None
LOCALE : None.UTF-8
pandas : 1.0.3
numpy : 1.18.4
pytz : 2020.1
dateutil : 2.8.1
pip : 20.0.2
setuptools : 46.1.3.post20200330
Cython : None
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : None
IPython : None
pandas_datareader: None
bs4 : None
bottleneck : None
fastparquet : None
gcsfs : None
lxml.etree : None
matplotlib : None
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : None
pytables : None
pytest : None
pyxlsb : None
s3fs : None
scipy : None
sqlalchemy : None
tables : None
tabulate : None
xarray : None
xlrd : None
xlwt : None
xlsxwriter : None
numba : None