RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility.
See original GitHub issueI’m running Python 3.5.2
and numpy 1.15.0
I’m seeing:
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
return f(*args, **kwds)
According to this stackoverflow question I shouldn’t see this warring as it was silence since numpy 1.8
Why do I see it? and does it means anything?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:34 (27 by maintainers)
Top 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 >Python warning numpy.dtype size changed, may indicate ...
RuntimeWarning : numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88 from .tslib import iNaT, NaT, Timestamp, Timedelta, ...
Read more >PYTHON : RuntimeWarning: numpy.dtype size changed, may ...
PYTHON : RuntimeWarning : numpy.dtype size changed, may indicate binary incompatibility [ Gift : Animated Search Engine ...
Read more >Python :RuntimeWarning: numpy.dtype size ... - YouTube
Python : RuntimeWarning : numpy.dtype size changed, may indicate binary incompatibility (5solution). No views 5 minutes ago.
Read more >Python :RuntimeWarning: numpy.dtype size ... - YouTube
Python : RuntimeWarning : numpy.dtype size changed, may indicate binary incompatibility (5solution) · Comments.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is a harmless. You can either ignore it or go back to 1.14.5. Will be fixed in the upcoming 1.15.1 Duplicate of #11628. Leave this one open until 1.15.1 is released
Upgrade to numy 1.15.2 could solve the problem.
conda install numpy=1.15.2