Numpy no longer support np.int - #1166
mikesmithcode wants to merge 25 commits into
Conversation
np.int has been deprecated so changed to int
|
This seems like a relatively easy fix to get BayesSearchCV working properly again. New here and no idea what it needs for this to get applied, but 2 months seems to be a long time for a simple update to be sitting. |
|
This is a simple update - please push this through. |
|
Any chances this will be sucessfully pushed anytime soon? |
|
Hi! I would love to be able to use the library in production! |
|
Lol everyone gotta go to transformer.py to manually update the two np.int |
|
Hi! Just wanted to let you know that I'm waiting for this to be pushed through as well :) |
|
Last update 2021 - Its time to assume that this repo is no longer being supported. |
|
let's get this updated |
|
Dead repo? |
ivanstepanovftw
left a comment
ivanstepanovftw
left a comment
There was a problem hiding this comment.
Remove any other changes than changing np.int to int.
|
+1 this, please merge |
|
In the meantime (possibly forever) do |
11 participants
Numpy 1.24 no longer support np.int
I replaced 2 x np.int with regular int in transformers.py which were causing code to crash with calls to gp_minimize. Code now runs successfully.