question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"size changed, may indicate binary incompatibility"

See original GitHub issue

What is that and how do I silence this warning?

../../pyarrow-test-3.6/lib/python3.6/site-packages/pyarrow/tests/test_cython.py:102: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>   ???
E   ValueError: pyarrow.lib.DictionaryMemo size changed, may indicate binary incompatibility. Expected 184 from C header, got 160 from PyObject
lib.pxd:75: ValueError

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
pitroucommented, Jul 16, 2019

Update: I managed to reproduce locally… but only with manylinux1, not manylinux2010!

Here is a manylinux1-produced wheel:

Python 3.7.3 (default, Apr  3 2019, 19:16:38) 
[GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyarrow as pa
>>> pa.lib.DictionaryMemo.__basicsize__
160

Here is a manylinux2010-produced wheel:

Python 3.7.3 (default, Apr  3 2019, 19:16:38) 
[GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyarrow as pa
>>> pa.lib.DictionaryMemo.__basicsize__
184
0reactions
tomriddle54commented, Jul 16, 2019

How can we create binary @pitrou

Read more comments on GitHub >

github_iconTop Results From Across the Web

RuntimeWarning: numpy.dtype size changed, may indicate ...
When import scipy, error info shows: RuntimeWarning: builtin.type size changed, may indicate binary incompatibility. Expected zd, got zd.
Read more >
ValueError: numpy.ndarray size changed, may ... - GitHub
Describe the bug Below error is thrown while importing nemo.collections.asr package Traceback (most recent call last): File " ", line 1, ...
Read more >
ValueError: numpy.ndarray size changed, may indicate binary ...
I'm answering to my own question. numpy >=1.20 is not available from Bullseye repository. So I decided to install it from pypi through...
Read more >
Pandas : ValueError: numpy.ufunc size changed, may indicate ...
Pandas : ValueError: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216 from C header, got 192 from PyObject ...
Read more >
ValueError: numpy.ndarray size changed, may indicate binary ...
After the new release of numpy 1.22.0 on Dec 31st, Databricks failed with this error for my existing Databricks Notebook Version 10.1 and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found