You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the apply the datetime returned is an object type
That is in general what happens when you mix timezones inside of a container:
In [8]: pd.Series([pd.Timestamp('today').tz_localize('US/Eastern'),
pd.Timestamp('today').tz_localize('US/Central')])
Out[8]:
02019-07-2018:00:52.167252-04:0012019-07-2018:00:52.167459-05:00dtype: object
So I think the issue may just be that transform tries to infer back to datetime when it probably should just leave as object, though cc @mroeschke for thoughts
Code Sample, a copy-pastable example if possible
Similar issue as #24198 in pandas 0.25.0
Problem description
The timezone in the transform should be preserved but it is not.
For the apply the datetime returned is an object type
df.info()
showsExpected Output
Should preserve timezone
And should return datetime
Output of
pd.show_versions()
[paste the output of
pd.show_versions()
here below this line]INSTALLED VERSIONS
commit : None
python : 3.7.3.final.0
python-bits : 64
OS : Windows
OS-release : 10
machine : AMD64
processor : Intel64 Family 6 Model 78 Stepping 3, GenuineIntel
byteorder : little
LC_ALL : None
LANG : None
LOCALE : None.None
pandas : 0.25.0
numpy : 1.16.3
pytz : 2019.1
dateutil : 2.8.0
pip : 19.1.1
setuptools : 40.8.0
Cython : 0.29.10
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : 4.3.4
html5lib : 1.0.1
pymysql : 0.9.3
psycopg2 : 2.8.2 (dt dec pq3 ext lo64)
jinja2 : 2.10.1
IPython : 7.5.0
pandas_datareader: None
bs4 : 4.7.1
bottleneck : None
fastparquet : None
gcsfs : None
lxml.etree : 4.3.4
matplotlib : 3.0.3
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : None
pytables : None
s3fs : None
scipy : 1.3.0
sqlalchemy : 1.3.3
tables : None
xarray : None
xlrd : None
xlwt : None
xlsxwriter : None
The text was updated successfully, but these errors were encountered: