-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
_tree.pyx: Use np.intp_t instead of int #1466
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
Shall we let this one opened? #1823 solved the most common problems. Yet, bugs may still arise with billions of rows and/or features. |
Maybe better leave it open :-/ |
Wouldn't it be better to wait for another test case that fails and then address it then, instead of keeping tracker bugs open like this? |
+1 |
Fine with me. I'll close this issue. |
As pointed out in #1458, the use of
int
for everything related to indexing numpy arrays might not be safe. @seberg recommends usingnp.intp_t
instead.The text was updated successfully, but these errors were encountered: