RuntimeWarning: greenlet.greenlet size changed
See original GitHub issueafter clean install on Ubuntu server 22.04 i get this error when i try to start the service,
<frozen importlib._bootstrap>:241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 152 from C header, got 160 from PyObject
Is there a fix for this error?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Runtime Warning - Greenlet.greenlet size changed??
RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144, got 128 return f(*args, **kwds).
Read more >greenlet.greenlet size changed, may indicate binary ... - GitHub
You've installed greenlet 0.4.17, which changed sizes. If you keep using it, your application will likely crash. You should upgrade gevent to a ......
Read more >Binary compatibility issue with greenlet - Redash Discourse
Looks like there has been a binary break introduced in greenlet 0.4.17 ... RuntimeWarning: greenlet.greenlet size changed, may indicate ...
Read more >gevent crash on Python 3.10 (python-x2go fails to build)
greenlet size changed, may indicate binary incompatibility. Expected 152 from C header, got 160 from PyObject <frozen importlib._bootstrap>:241: ...
Read more >Bug#1024595: python3-gevent 22.10.2 must depend on ...
_bootstrap>:241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, ...
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 FreeTop 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
Top GitHub Comments
okay, ill try again then with a new ubuntu installation. but thats for tomorrow.
Hello,
Can you please try the following :
and let me know if this fixs the issue ? It worked in my test environment, but I must test the compatibility with older releases.
Arnaud