-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Timestamp timezone inconsistency #8656
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
Comments
These all represent exactly the same time
|
This works fine for me as well. So either check with pandas master or an updated pytz (although I would find the latter really hard to believe since there is nothing special with this offset).
|
actually I think this was #7833 which was fixed for 0.15.0 |
Great, thanks! Didn't realize RC is the stable version now. Yes, they both represent the right UTC time, but one of them didn't have
|
I wouldn't call RC the stable version (however it is pretty stable and everything that gets merge needs to pass all the tests). v0.15.0 is the latest release and this is fixed there. |
0.15.0 is the stable version released that week |
Hi,
Is this a known issue?
Time offset on 22nd of Sept should be -4 hours in New York as below:
but when providing this twice (-0400 and EST4EDT), the result becomes -0500:
Thanks,
Mark
INSTALLED VERSIONS
commit: None
python: 2.7.6.final.0
python-bits: 64
OS: Linux
OS-release: 3.13.0-37-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_GB.UTF-8
pandas: 0.14.1
nose: 1.3.0
Cython: 0.19.2
numpy: 1.8.1
scipy: 0.13.2
statsmodels: 0.5.0
IPython: 2.0.0
sphinx: None
patsy: 0.2.1
scikits.timeseries: None
dateutil: 2.2
pytz: 2014.2
bottleneck: 0.8.0
tables: 3.0.0
numexpr: 2.3
matplotlib: 1.3.1
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: 0.999
httplib2: 0.8
apiclient: None
rpy2: None
sqlalchemy: None
pymysql: None
psycopg2: None
The text was updated successfully, but these errors were encountered: