-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
COMPAT: dateutil fixups for 2.3 (GH9021, GH8639) #9036
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
Conversation
ok, this shows the failures (scroll way to the end): https://travis-ci.org/jreback/pandas/jobs/43281972 |
cc @dbew |
this mostly fixes the issues so going to merge this. |
COMPAT: dateutil fixups for 2.3 (GH9021, GH8639)
I get massive test failures similar to travis. Any ETA for a fix of those? |
are u sure that u updated to master and recompiled |
...... ERROR: test_timestamp_tz_convert (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): ERROR: test_utc_with_system_utc (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): ERROR: test_with_tz (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): ERROR: test_tz_convert_roundtrip (test_timezones.TestTimeZones)Traceback (most recent call last): FAIL: test_ambiguous_flags (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_ambiguous_infer (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_ambiguous_nat (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_datetimeindex_tz_nat (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_frame_no_datetime64_dtype (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_index_with_timezone_repr (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_infer_tz (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_localize_utc_conversion (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_localize_utc_conversion_explicit (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_timedelta_push_over_dst_boundary (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_timedelta_push_over_dst_boundary_explicit (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_tz_localize_dti (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_utc_box_timestamp_and_localize (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_with_tz_ambiguous_times (test_timezones.TestTimeZoneSupportDateutil)Traceback (most recent call last): FAIL: test_tz_localize_roundtrip (test_timezones.TestTimeZones)Traceback (most recent call last): Ran 135 tests in 0.524s FAILED (SKIP=2, errors=4, failures=15) |
INSTALLED VERSIONScommit: None pandas: 0.15.1-213-g67ec0a8 |
you need to
you didn't recompile I was able to repro the problem, and the single original test failure remains (but is actually a larger problem). datetutil 2.3 broke the API (again :()), this was release a few days ago easiest is simply to downgrade to 2.2. or use pytz timezones which are the default anyhow |
I did recompile, but I didn't paste the log here. |
you are showing me a build log for 3.3. Pls humor me. Just clone the repo in a new directly, compile and test on 2.7. Where are you seeing a travis failure (again except for the final build, which has 2 test failures)? |
Just scroll up, there is the test failure for 2.7. And believe me, I am experienced enough in building packages that you don't need to treat me as a stupid noob. The failure is there on python 2.7, 3.3 and 3.4. |
@jlec I appreciate you are trying to help. Pls downgrade to 2.2 |
This is plain python-2.7 with current HEAD and python-dateutils-2.2 |
so since this is not happening on any other linux (for 2.2), then something different between what you are doing and say travis. maybe you can help figure that out. IIRC you had this problem with 0.15.0 as well? |
With 0.15* I had #8639 But I am retesting right now. |
So current HEAD and 0.15.1 show different problems using dateutil-2.2 |
fixes #9021
but going to reopen #8639