C3_W1_Lab_2_TFX_Tuner_and_Trainer grpc

Course Q&A Machine Learning Engineering for Production(MLOps) Machine Learning Modeling Pipelines in Production
1

Hello, I get “google-api-core 2.11.0 has no such extra feature ‘grpc’” when I try to import dependencies. Do you know what is the reason?

2

It’s possible that you didn’t restart the runtime after installing the libraries and before importing the dependencies.
I just ran the cells and there is no error.

Please confirm.

3

No, still does not work.

I see 2 things:

  1. when I install packages - ERROR: pip’s dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
    xarray 2022.12.0 requires packaging>=21.3, but you have packaging 20.9 which is incompatible.
    statsmodels 0.13.5 requires packaging>=21.3, but you have packaging 20.9 which is incompatible.
    pandas-profiling 3.2.0 requires joblib~=1.1.0, but you have joblib 1.2.0 which is incompatible.
    google-cloud-firestore 2.7.3 requires google-api-core[grpc]!=2.0.,!=2.1.,!=2.10.,!=2.2.,!=2.3.,!=2.4.,!=2.5.,!=2.6.,!=2.7.,!=2.8.,!=2.9.*,<3.0.0dev,>=1.34.0, but you have google-api-core 1.32.0 which is incompatible.
    flask 2.2.3 requires click>=8.0, but you have click 7.1.2 which is incompatible.

  2. when I try importing tfx - [Errno 2] No such file or directory: ‘/usr/local/lib/python3.9/dist-packages/google_api_core-2.11.0.dist-info/METADATA’

1 Like
4

There are errors in the install section and the staff have been notified about it.
I’m still able to run the imports without a problem (please see screenshot below):

image
image1081×378 40.8 KB

5

Hi Denis! I just tried it out and only see that error if I don’t restart the runtime after the install. After running the pip install cell, please click Runtime > Restart Runtime and then run the next cell (i.e. imports). The problem goes away for me after that.

As also stated in the note after installation, you can ignore the errors about version incompatibility of some of the bundled packages.

I also remember from one previous experience: my Colab runtime was reset for no apparent reason, and I had to reinstall the packages again. That might have happened to you that’s why the restart didn’t work as expected. It rarely happens though so you can expect it to work normally moving forward.

Hope this helps!