-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
BUG: Add np.uintc to _factorizers in merge.py to fix KeyError when merging DataFrames with uintc columns #58727
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
Changes from 3 commits
1774489
5372107
3d75d94
0f79322
2c18b6b
1373e05
16adf4b
523efa4
f3de1f9
67297bd
61ff0e2
c05255a
87cb28d
2adb5fc
88a1618
90e0b93
1b9e3d0
4da0b86
95bca2c
a37151e
c5a3ccc
402c33c
7438297
9105c97
e3b76a1
8506f78
621c8d1
50fe143
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1491,9 +1491,12 @@ def test_different(self, dtype): | |
result = merge(left, right, on="A") | ||
assert is_object_dtype(result.A.dtype) or is_string_dtype(result.A.dtype) | ||
|
||
@pytest.mark.parametrize( | ||
"d1", [np.int64, np.int32, np.intc, np.int16, np.int8, np.uint8] | ||
) | ||
Tirthchoksi22 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
@pytest.mark.parametrize("d2", [np.int64, np.float64, np.float32, np.float16]) | ||
def test_join_multi_dtypes(self, any_int_numpy_dtype, d2): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you keep this test the same and add a new separate test for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok sure |
||
dtype1 = np.dtype(any_int_numpy_dtype) | ||
def test_join_multi_dtypes(self, d1, d2): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So it appears that this has been updated since the last fix. I doubt that this should be changed. it's probably that However, So looks like will need to add both There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ok i will add it in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you explain the issue to me (as I don't have the platform to test) Although my previous comment was to align better with the previous fix, I don't know why we need to explicitly cater for So adding these does not really make sense to me as I don't really understand the issue. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @simonjayhawkins what i think is the issue arises because certain functionalities within There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @simonjayhawkins I still didnt understand why regression occur on windows side perhaps compatibility issue ??? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @simonjayhawkins if you think to change this according to last fix then tell me as this fix will also work There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
well it works on other platforms, so it maybe not a pandas issue? |
||
dtype1 = np.dtype(d1) | ||
dtype2 = np.dtype(d2) | ||
|
||
left = DataFrame( | ||
|
Uh oh!
There was an error while loading. Please reload this page.