flask-restful | Simple framework for creating REST APIs | REST library

The scikit-learn library is a different version on your cloud machine.

Specifically, the sklearn.neighbors._dist_metrics was removed around version 1.0.2. Perhaps your docker container is not actually using your requirements.txt properly.

Here's an example of different versions:

This one doesn't throw an error

the main difference between Flask-RESTx and Flask-RESTful is that Flask-RESTx supports auto-generated Swagger documentation. i think there are no other noticeable differences.

From the documentation:

URL

one or more url routes to match for the resource, standard flask routing rules apply. Any url variables will be passed to the resource method as args.

ENDPOINT

endpoint name (defaults to Resource.name.lower() Can be used to reference this route in fields.Url fields

The endpoint parameter must be specified when you intend to manage two or more urls with the same class, in fact, considering the following code snippet:

Currently reqparse will handle only JSON objects as body (source: will fail on any other object except dict and MultiDict), and not any other type. You'll have to grab the request object directly for your needs.

One way to fall back on the database-side default value is to NOT provide data for a particular column in the insert.

In that case, the server will insert the default value for that column. If you did not specify a default value in the CREATE TABLE (or later ALTER TABLEs) than that default value is NULL (which corresponds to Python None).

However, since col2 does have a database-specified default, via col2 TEXT DEFAULT "global" NOT NULL, then not specifying col2 in the insert will instead cause sqlite to use "global". Ditto col3.

You can build the query dynamically, to exclude columns with None, as long as you are careful with what you compose into the query string.

I was able to reproduce your issue. If you look at the logs inside cloud functions, it says there's an ssl certificate error.

I tried changing your requirements.txt to not include a version number on requests and it worked:

Are you sourcing your venv before running test.py?

If so, then try this,

Searching for the exception, leads to the corresponding eventlet issue: https://github.com/eventlet/eventlet/issues/687

The summary is that eventlet (0.32.0) is currently not compatible with Python 3.10 because it tries to patch types that have become immutable in Python 3.10.

Like with your requirements, it is good practice to be more specific with your Docker dependencies too. Today using the tag 3 for the Python Docker image will give you 3.10.0, unless it is using a cache. In the future it could be a different version. Since there is a compatibility issue with Python 3.10, use Python 3.9 - the currently latest Python 3.9 Docker tag is 3.9.7.

i.e. it should work once you change your first line of the Dockerfile to:

If you have a look for the base image, you could see it just be updated 27hours ago.