[issue28636] strange issue with Pandas-0.19.1 on Python-3.6.0b3

2016-11-08 Thread Big Stone
Big Stone added the comment: Thank you, Victor. So I guess I should close the issue. -- status: open -> closed ___ Python tracker ___

[issue28636] strange issue with Pandas-0.19.1 on Python-3.6.0b3

2016-11-07 Thread STINNER Victor
STINNER Victor added the comment: > while with python < 3.6, you get a "ValueError" It's because Python 3.6 is more strict. Python 3.5 doesn't catch the bug. -- ___ Python tracker _

[issue28636] strange issue with Pandas-0.19.1 on Python-3.6.0b3

2016-11-07 Thread Big Stone
Big Stone added the comment: the curiosity is the error message, different (and uncaught) under Python 3.6 "SystemError", while with python < 3.6, you get a "ValueError" -- ___ Python tracker __

[issue28636] strange issue with Pandas-0.19.1 on Python-3.6.0b3

2016-11-07 Thread STINNER Victor
STINNER Victor added the comment: Extract of the bug report: > ... > pandas/tslib.pyx in pandas.tslib.convert_str_to_tsobject > (pandas/tslib.c:26851)() > pandas/src/datetime.pxd in datetime._string_to_dts (pandas/tslib.c:87106)() > SystemError: returned a result with an error set It looks li

[issue28636] strange issue with Pandas-0.19.1 on Python-3.6.0b3

2016-11-07 Thread Big Stone
New submission from Big Stone: hi, we detect a strange issue on Pandas-0.19.1/Python-3.6.0b3/Windows that may or may not be a Python-3.6 bug. As it was for the glory of Python-3.6.0b3 testing, we signal the incident here. https://github.com/pandas-dev/pandas/issues/14561 -- messages: 2