-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: roundtrip fidelity for a tz-aware DTI with a fixed format HDFStore #17618
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.
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
Labels
Milestone
Comments
you are saving in This is quite similar to this bug: #11926. This also works when the tz-aware data is a column (and not an index); but you will get a warning as its trying to pickle the objects; this is not very performant. Would gladly take a PR to fix, and its not that hard. |
|
jjhelmus
added a commit
to jjhelmus/pandas
that referenced
this issue
Oct 11, 2017
Set the tz after creating the DatetimeIndex instance when reading from a fixed format HDFStore. Setting the tz during instance creation offset data. closes pandas-dev#17618
jjhelmus
added a commit
to jjhelmus/pandas
that referenced
this issue
Oct 11, 2017
Set the tz after creating the DatetimeIndex instance when reading from a fixed format HDFStore. Setting the tz during instance creation offset data. closes pandas-dev#17618
4 tasks
jjhelmus
added a commit
to jjhelmus/pandas
that referenced
this issue
Oct 11, 2017
Set the tz after creating the DatetimeIndex instance when reading from a fixed format HDFStore. Setting the tz during instance creation offset data. closes pandas-dev#17618
jreback
pushed a commit
that referenced
this issue
Oct 13, 2017
buntwo
pushed a commit
to buntwo/pandas
that referenced
this issue
Oct 14, 2017
ghost
pushed a commit
to reef-technologies/pandas
that referenced
this issue
Oct 16, 2017
alanbato
pushed a commit
to alanbato/pandas
that referenced
this issue
Nov 10, 2017
No-Stream
pushed a commit
to No-Stream/pandas
that referenced
this issue
Nov 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code Sample, a copy-pastable example if possible
Problem description
The output of the above code sample is:
I would expect the outputs to be the same in all these cases. The error occurs after saving and loading a DataFrame with a timezone aware index. The index remains timezone aware but the index value changes to an incorrect value. This incorrect value seems to be the value it would have if the local time were actually UTC time. This error occurs for an index with multiple entries as well.
Expected Output
Output of
pd.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.6.2.final.0
python-bits: 64
OS: Linux
OS-release: 3.10.0-514.21.1.el7.x86_64
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
pandas: 0.20.3
pytest: None
pip: 9.0.1
setuptools: 36.3.0
Cython: None
numpy: 1.12.1
scipy: 0.19.1
xarray: 0.9.6
IPython: 6.2.0
sphinx: None
patsy: 0.4.1
dateutil: 2.6.1
pytz: 2017.2
blosc: None
bottleneck: 1.2.1
tables: 3.4.2
numexpr: 2.6.4
feather: None
matplotlib: 2.0.0
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: 0.999999999
sqlalchemy: None
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None
The text was updated successfully, but these errors were encountered: