Hello Guys How Are You All ? Hope You all are fine. Today I Have Faced In Python. **ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject.** numpy.ndarray size changed, may indicate binary incompatibility.So Here I am Explain to you all the possible solutions Here.

Without Wasting your time, Lets start This Article to Solve This Error in Anaconda

Table of Contents

## How ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject Occurs?

Importing from pyxdameraulevenshtein gives the following error, I have

```
pyxdameraulevenshtein==1.5.3,
pandas==1.1.4 and
scikit-learn==0.20.2.
Numpy is 1.16.1.
Works well in Python3.6, Issue in Python3.7.
```

Has anyone been facing similar issues with Python3.7 (3.7.9), docker image – python:3.7-buster

```
__init__.pxd:242: in init pyxdameraulevenshtein
???
E ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject
```

## How to Solve ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject?

**Solutions**:

**Question: ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject?**

Answer: Expected 88 from C header, got 80 from PyObject … try with numpy==1.20.0 this worked here, even though other circumstances are different (python3.8 on alpine 3.12). … There was a change in the C API in numpy 1.20.0 . … (The other way around it should not matter, because of backwards compatibility.

**Solution 1**

I’m in Python 3.8.5. It sounds too simple to be real, but I had this same issue and all I did was reinstall numpy. Gone.

```
pip uninstall numpy
pip install numpy
```

**Solution 2**

try with `numpy==1.20.0`

this worked here, even though other circumstances are different (python3.8 on alpine 3.12).

**Solution 3**

I had this issue when using the tensorflow object api. Tensorflow is currently NOT compatible with numpy==1.20 (although this issue is not apparent until later). In my case, the issue was caused by pycocotools. I fixed by installing an older version.

`pip install pycocotools==2.0.0`

**Soution 4**

Indeed, (building and) installing with `numpy>=1.20.0`

should work, as pointed out. However, I thought some background might be interesting — and provide also alternative solutions.

There was a change in the C API in `numpy 1.20.0`

. In some cases, `pip`

seems to download the latest version of `numpy`

for the build stage, but then the program is run with the installed version of `numpy`

. If the build version used in `<1.20`

, but the installed version is `=>1.20`

, this will lead to an error.

(The other way around it should not matter, because of backwards compatibility. But if one uses an installed version `numpy<1.20`

, they did not anticipate the upcoming change.)

This leads to several possible ways to solve the problem:

- upgrade to
`numpy>=1.20.0`

- use
*minmum supported numpy*version in pyproject.toml (`oldest-supported-numpy`

) - install with
`--no-binary`

- install with
`--no-build-isolation`

**Summery**

It’s all About this issue. Hope all solution helped you a lot. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?