pip install DEPENDNECY ERROR on macOS #14573
Assignees
Comments
|
This is affecting my team as well. |
|
Currently this makes installing TensorFlow 1.6 for macOS through pip fail. |
|
For some reason our build infrastructure did not generate the macOS binary wheels and they were not uploaded to PyPI; consequently, pip install is trying to compile from source |
|
macOS binary wheels are uploaded. Should be fixed now. Please retry (ensure pip is not fetching from cache and taking the binary from PyPI). |
|
@hhusum @levi-rs can y'all please retry and let me know if it got fixed for you? |
|
@mehrdada Works for me! Thank you for the quick turnaround. |
|
Works for me as well! Good job. |
|
Works for me ! Cool |
|
I'm getting the same while installing https://github.com/firebase/firebase-admin-python fetching 1.10.1 version. Maybe still Mac OS packages for this version are not on PyPI? |
|
@francbartoli I can see macOS binaries uploaded here: https://pypi.python.org/pypi/grpcio/1.10.1. I just verified it on my Mac running High Sierra: |
|
Still failing: |
|
@francbartoli Looks like it somehow picks up OpenSSL headers on your system installed with brew instead of the shipped BoringSSL. Can you try force installing the binary wheels? |
|
@mehrdada strange the package seems to be not reachable: |
|
@francbartoli Let's file a new issue with details of your system, version of OS, Python, pip, etc to investigate. The root cause seems unrelated to this one. |
|
@mehrdada It worked for me. I was trying to install dialogflow. I used this |
work for me ,thanks @Mehrdata |
I'm getting the same error. Did you find a fix for this? |
|
Same error. |
|
@erickertz @iniyanp Please file a new issue with the details of your environment. I believe the original issue here is fixed. Also, please avoid using 1.10.1, as the current version (uploaded 17 hours ago) is 1.16.0. Please do let us know if there is trouble with that. |
|
@mehrdada I am experiencing the same exact issue with 1.16.0 though. |
|
@erickertz On what platform/version? |
|
@erickertz FYI |
OSX El Captain 10.11.6 . Python 2.7.11 . If I do pip install grpcio==1.16.0 the same exact error occurs as stated by the OP. |
|
python installed with pyenv |
|
@lidizheng can you try reproducing with |
|
Just wanted to add if its any help that I was able to get the same setup that @erickertz was trying to run to work with python 2.7.15 installed natively from the macOS installer on python.org. |
|
@mehrdada |
|
This is only happening on my OSX machine, btw
…On Wed, Oct 24, 2018 at 4:48 PM Lidi Zheng ***@***.***> wrote:
@mehrdada <https://github.com/mehrdada> pyenv with Python 2.7.11 can't
reproduce the error...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14573 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGHbGLycTaMcAUgD3XMFGQlW7FmzINxSks5uoNIFgaJpZM4SZf-q>
.
|
|
@erickertz I'm in 10.13.6. Can you provide the log of |
|
@erickertz At here, it shows the problem is that your system might be included your local OpenSSL before building gRPC which uses BoringSSL. It usually happened because of compiler flags being customized somewhere. Can you try to install gRPC in a clean environment? Like # Use another user to install
sudo pip install -vvv grpcio# Disable your ~/.profile or ~/.bash_profile or ~/.bashrc
bash --noprofile --norc
$ # Install inside the bash
$ pip install -vvv grpcio |
|
Please note that if issues were closed, we shouldn't reopen them for different problems. This seems like a different problem. Please leave the issue closed and open a new issue instead. |
|
I agree—now that we are confident this is a different issue, I'm closing it. Let's track it on a separate issue. |
|
Same issue with PyPy installed from MacPorts Log: |
Was there a new issus created for this? Seems there are multiple people experiencing the same error. Thanks. |
|
@Mottl @BillG18 I think I found a workaround for this. The sudo and noprofile suggestions by @lidizheng unfortunately did not work for me. However, installing with sudo, nocache, and pointing directly to the tz did. try like this:
Also note that I completely removed my venv and created a new one before running this. Hope this helps and continues to work. |
|
Thanks. Unfortunately, it doesn't work — the error is the same. As stated above the problem is related to the already installed openssl library. |
|
@Mottl sorry to hear. I did also install boringssl manually before I ran. Not sure if that allowed it to work for me:
|
|
The original issue (no macos support for grpc 1.10.1) was initially resolved. Please do stop confounding multiple issues into a single bug report, that'll only create confusion and frustration, and open a new github issue to explain and discuss the new one instead. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Python 2.7.14 :: Anaconda custom (64-bit)
macOS:10.13.3
The text was updated successfully, but these errors were encountered: