Skip to content
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

ValueError: numpy.ndarray size changed, may indicate binary incompatibility. #236

Closed
maciejbiesek opened this issue Jan 7, 2022 · 9 comments

Comments

@maciejbiesek
Copy link

A few days ago the problem with ValueError: numpy.ndarray size changed, may indicate binary incompatibility. occurred during executing the code that worked one week ago without any problems.

The same issue is with BERTopic (MaartenGr/BERTopic#392), so I thought maybe it would be beneficial to link it there. For now, it seems there is no easy solution to that problem

@ddangelov
Copy link
Owner

What embedding_model did you use and during which step did you get this error?

@Uzay-G
Copy link

Uzay-G commented May 3, 2022

I get this also with universal sentence decoder when I import top2vec. I think it's because on python 3.10, numba requires numpy <=1.21 but gensim requires numba >=1.22 (https://github.com/RaRe-Technologies/gensim/blob/93ed2fbe27dab41b459bd09bd5b19ed5d7e01908/.github/workflows/build-wheels.yml#L95).

So the library is not usable for python3.10

@Uzay-G
Copy link

Uzay-G commented May 3, 2022

How to fix this: use python < 3.10, use numpy <= 1.21

@Uzay-G Uzay-G mentioned this issue May 3, 2022
@ddangelov
Copy link
Owner

I have no issues with this and I have python 3.8.5 so I don't think that is the issue.

@Uzay-G
Copy link

Uzay-G commented May 4, 2022

The problem is with python 3.10

@ddangelov
Copy link
Owner

setup.py specifies python_requires='>=3.6'

@Uzay-G
Copy link

Uzay-G commented May 4, 2022

3.10 is >= 3.6?

I don't mean 3.1, python 3.10 (https://www.python.org/downloads/release/python-3100/) was released in october.

@Uzay-G
Copy link

Uzay-G commented May 4, 2022

It's not an old release.

@ddangelov ddangelov reopened this May 4, 2022
@ddangelov
Copy link
Owner

Ok got it. Will investigate.

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

No branches or pull requests

3 participants