-
Notifications
You must be signed in to change notification settings - Fork 933
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.1.1 gevent/ares.so: undefined symbol: PyUnicodeUCS2_DecodeUTF8 #789
Comments
That looks pretty much the same as #549 to me. How did you install gevent? Specifically, did you use a manylinux binary wheel from PyPI or did you build it from source? There are manylinux wheels posted for both wide and narrow builds on PyPI, and it looks like you got the narrow build but needed the wide build. Perhaps your pip needs upgrading to get the right wheel (you may also need to clear your local pip cache). A workaround might be to compile from scratch using the --no-binary argument of pip. |
We did Output:
pip version:
Not sure whether |
The 'mu' builds are the most commonly used builds; gevent 1.1.0 only uploaded 'mu' builds. These were built with the official pypa/manylinux docker image, which was updated between 1.1.0 and 1.1.1; in the 1.1.0 time frame it didn't include the 'm' version (hence why they're missing). I'm not sure what to tell you about how to investigate further. My two recommendations at this point would be to use the --no-binary option to build from source (to fix your immediate problem), and to open up an issue with the manylinux people (and CC me) who should have a much better idea about how their official builds could result in a situation like this. |
Thank you @jamadden I'm not entirely sure what to report on at manylinux repo, as I'm not familiar with the whole build process and this tool/platform. |
Ok, I opened pypa/manylinux#49 |
@jamadden thank you again, very much! |
I've pulled the effected wheel from PyPI (since having linux wheels is a very new thing, I suspect most linux users are used to compiling gevent and so that shouldn't be a problem). The manylinux guys are working on toolchain improvements to help prevent this from happening again. |
Note: I think this is a bit different from #549
After updating from version
1.1.0
to1.1.1
, under the same environment:Python (virtualenv from OS Python 2.7):
OS:
It gives me this error:
We use gevent as gunicorn's async worker to run a flask web app. Reverting to
1.1.0
resolves this issue.The text was updated successfully, but these errors were encountered: