No module named "grpc_interceptor" error

[AmandaHassoun]

Environment details

• OS type and version:
• Python version: 3.11
• google-cloud-spanner version: 3.49.0, so latest release

Steps to reproduce

1. Attempt to download google-cloud-spanner==3.49.0
2. Attempt to insert a record into a Spanner instance.

Stack trace

ModuleNotFoundError: No module named 'grpc_interceptor'
Traceback (most recent call last):
  ....
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner.py", line 17, in <module>
    from google.cloud.spanner_v1 import __version__
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner_v1/__init__.py", line 70, in <module>
    from google.cloud.spanner_v1.client import Client
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner_v1/client.py", line 50, in <module>
    from google.cloud.spanner_v1.instance import Instance
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner_v1/instance.py", line 37, in <module>
    from google.cloud.spanner_v1.testing.database_test import TestDatabase
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner_v1/testing/database_test.py", line 25, in <module>
    from google.cloud.spanner_v1.testing.interceptors import (
  File "/usr/lib/python3.11/site-packages/google/cloud/spanner_v1/testing/interceptors.py", line 16, in <module>
    from grpc_interceptor import ClientInterceptor
ModuleNotFoundError: No module named 'grpc_interceptor'

I suspect this is related to this recent commit.

[cchabilall83]

I recently encountered the same issue we've using the spanner client with no issue for months and it's failing today.

Python version: 3.10

File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner.py", line 17, in <module>
    from google.cloud.spanner_v1 import __version__
  File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner_v1/__init__.py", line 70, in <module>
    from google.cloud.spanner_v1.client import Client
  File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner_v1/client.py", line 50, in <module>
    from google.cloud.spanner_v1.instance import Instance
  File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner_v1/instance.py", line 37, in <module>
    from google.cloud.spanner_v1.testing.database_test import TestDatabase
  File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner_v1/testing/database_test.py", line [25](https://github.com/nicejobinc/ai-ui-agent/actions/runs/10705101662/job/29679667449#step:5:26), in <module>
    from google.cloud.spanner_v1.testing.interceptors import (
  File "/opt/hostedtoolcache/Python/3.10.11/x64/lib/python3.10/site-packages/google/cloud/spanner_v1/testing/interceptors.py", line 16, in <module>
    from grpc_interceptor import ClientInterceptor
ModuleNotFoundError: No module named 'grpc_interceptor'

[potiuk]

Same for Apache Airflow - https://github.com/apache/airflow/actions/runs/10708266123/job/29690485827#step:7:4358. our tests started to fail after 3.49.0 release today

[rbarrette]

Also running into this issue today!

[rbarrette]

Looks like 3.49.0 moved grpc-interceptor to extras/testing. When I test locally with google-cloud-spanner[testing] in requirements, grpc-interceptor is installed.

[potiuk]

Looks like 3.49.0 moved grpc-interceptor to extras/testing. When I test locally with google-cloud-spanner[testing] in requirements, grpc-interceptor is installed.

Which is problematic because you do not want all the extra test dependencies when you have "production" dependency specification. For now I just added !=3.49.0 in Airflow and hope it is going to be fixed in 3.49.1 (in which case it will be automatically picked up and tested by Airflow)

[rbarrette]

@potiuk

Here is the specific change. I agree with you when it comes to avoiding test dependency pollution. Looks like that is the only dependency in the testing extra. I opened a PR over at airflow, but might be best to wait and see if the google-cloud-spanner team reverts this change, or commits to this or another path forward.