Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

Numpy no longer support np.int #1166

Open
wants to merge 25 commits into
base: master
Choose a base branch
from

Conversation

mikesmithlab
Copy link

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.

@Tom-Schipper
Copy link

Tom-Schipper commented Jul 12, 2023

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.

@RobertHH-IS
Copy link

This is a simple update - please push this through.

@NikoMak
Copy link

NikoMak commented Nov 17, 2023

Any chances this will be sucessfully pushed anytime soon?

@scallon
Copy link

scallon commented Nov 29, 2023

Hi! I would love to be able to use the library in production!

@BingnanHuo
Copy link

Lol everyone gotta go to transformer.py to manually update the two np.int

@lene-hansen
Copy link

Hi! Just wanted to let you know that I'm waiting for this to be pushed through as well :)

@RobertHH-IS
Copy link

Last update 2021 - Its time to assume that this repo is no longer being supported.

@davidhaan
Copy link

let's get this updated

@ivanstepanovftw
Copy link

Dead repo?

Copy link

@ivanstepanovftw ivanstepanovftw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove any other changes than changing np.int to int.

@janton10
Copy link

+1 this, please merge

@micycle1
Copy link

micycle1 commented Feb 7, 2024

In the meantime (possibly forever) do np.int = int.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet