# One of solution about "ValueError: numpy.dtype size changed" when running .yml on Github

One of solution about "ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject" when running {workflow}.yml on Github to build pyhton to .exe.

Environment
---
- python : 3.9
- pyinstaller : 5.9.0
- ==numpy : 1.22.3==
- pyhton on workflow : 3.10
- pyinstaller server get auto : 6.9.0
- ==numpy server get auto : 2.0.0==

Heppend
---
In begin, I know my local version of ==python and pyinstaller== is different from the latest one on the server, but this error shouldn't occur either.
>ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
Error: Process completed with exit code 1.

I just modified some judgments as same format before and the regular expression to filter the file.
[My Code change](https://github.com/yishawnpeng/HpBIOS_ReleaseNote_Check/commit/f750f7b15b7fdfa4add9462284382c39fe2c5ecc)

.Yml
---
Just build python to exe as usual.

- name: Set VERSION variable for windows
  run: |
    echo "VERSION=$(python compare_BCU_RN.py --version)" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append

[Complete .Yml on my Github](https://github.com/yishawnpeng/HpBIOS_ReleaseNote_Check/blob/main/.github/workflows/Python_build.yml)

Root Cause
---
Then I found out maybe the version of numpy is wrong.
Because I don't use new feature of numpy but accur error.
So I search the log of {workflow}.yml at part of "Build with PyInstaller for windows"

  run: |
    pyinstaller `
      --onefile compare_BCU_RN.py `
      --python-option u `

And confirmed it installed ==numpy version 2.0.0==.
> ...
*Collecting numpy>=1.21.0 (from pandas==1.3.5->-r requirements.txt (line 1))
Downloading numpy-2.0.0-cp310-cp310-win_amd64.whl.metadata (60 kB)*
...

Solution
---
Very eazy, just let {workflow}.yml to install the numpy version you use.

==Error Fixed !!==

Of course, it will be better to update the locally used NUMPY version when developing in the future, but it is also possible that FORAML CODE may have other unexpected issues due to updating it.
:cry::cry::cry::cry::sweat::sweat::sweat::sweat:

Reference
---
- [Stack overflow - RuntimeWarning: numpy.dtype size changed...](https://stackoverflow.com/questions/40845304/runtimewarning-numpy-dtype-size-changed-may-indicate-binary-incompatibility)
- [CSDN - RuntimeWarning: numpy.dtype size changed...](https://wenku.csdn.net/answer/14v403ni0w)

###### tags: `ValueError: numpy.dtype size changed` `.yml` `workflow` `Github` `pandas` `pyinstaller` `version`