-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
pip install cryptography segmentation fault (SIGSEGV) #3815
Comments
Can you say a little more about how you produced this case? I just spun up a Zesty docker container, ran Failing that, if you can reproduce this consistently, can you get a core dump? |
Thanks for the quick response @alex! I have the
And I don't have I'm also running it in a virtual machine, on VMWare Fusion 8.5.8. I tried in Bash as well in case it was shell-related, but it's the same. I was actually trying to run It happens every time, I've uploaded a core dump taken just now here: https://transfer.sh/10LTxK/_usr_bin_pip.1000.crash This is stored by Ubuntu's |
Hmmm, I'm having trouble getting
|
So, yes I have the same problem with names in the stack (just "??"). As a guess, I installed the
|
I resolved the issue while attempting to get Sorry for the errant error report. Hopefully this saves someone else some time too! |
Thanks for letting us know the resolution of this. |
|
FWIW I was having this same segfault on raspbian. I removed python-cryptography, was still segfaulting. I called pip3 with |
No. Just no.
This is NOT a workable solution |
The actual fix is in pypa/pip#5366 |
Following @tedder instruction, removed apt package and installed pip package fixed for me.
|
As I said before that is the exact wrong solution and only encourages the already terrible deb package support from devs who do not want anyone to use debs. |
There is a absolutely no excuse for closing this bug |
We don't have any deb package support at all! We provide cryptography as an sdist, and a wheel, the standard python packaging formats. To the extent there's a conflict with installing using |
Consider this a gentle reminder that the strangers you yell at about software on the internet are almost always volunteers and that statements like "There is a absolutely no excuse for closing this bug" are not likely to produce a positive outcome. As always, we are absolutely willing to fix bugs in our software, but Python is a platform and frequently bugs like this are outside of our ability to control. In this situation, having multiple different versions of our library installed in different locations caused Python to inappropriately load parts of each version. The "correct" fix here is to use a virtualenv or in some fashion isolate your environments such that you don't bleed system packages into pip installed packages and there is no library-level fix we can apply. |
Running
pip install cryptography
results in a segmentation fault at the end and I'm not sure where to even start fixing this! Here is my log:I tried the
-vvv
flag, which added this at the end:OS details:
pip install
seems to work fine with other packages, hence the bug report here, but please let me know if it's in error!The text was updated successfully, but these errors were encountered: