Skip to content

Cannot import name 'cygrpc' from 'grpc._cython'

Hanzhang Zeng edited this page Jul 1, 2020 · 3 revisions

Python interpreter mismatches operating system's bitness

This is most likely caused by a 32-bit Python interpreter is installed on a 64-bit Windows system.

If you're running on Windows x64, please ensure your Python 3.6, 3.7, or 3.8 interpreter is also on 64-bit version. This can be checked by simply open a cmd.exe or powershell.exe and type in py to launch the Python interpreter. The header should tell if you're running on 64 bit or 32 bit (e.g. [MSC v.1916 64 bit (AMD64)]).

C:\Users\worker>  py
Python 3.8.1 (tags/v3.8.1:...) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

If not, please uninstall Python in your machine, and download the x64 interpreter from release page (e.g. https://www.python.org/downloads/release/python-383/) Windows x86-64 executable installer.

Python interpreter is not supported by Azure Functions Python Worker

Azure Functions only supports in Python 3.6, Python 3.7, and Python 3.8. Please check if your Python interpreter matches our expected version. This can be done by simply using py --version in Windows or python3 --version in Linux. Ensure the return result is Python 3.6.x, Python 3.7.x, or Python 3.8.x.

Missing local.settings.json

If you're using Azure Functions Core Tools or Visual Studio Code for debugging your local project, you need to double check if local.settings.json file exists in your project root. If not, please consider using func init --python to generate one.