Could not load Google Cloud Storage bindings with `django-storages==1.14.6`

[HitLuca]

Getting this error when start my django project, pages don't load and get this erro on the console

django.core.exceptions.ImproperlyConfigured: Could not load Google Cloud Storage bindings.
See https://github.com/GoogleCloudPlatform/gcloud-python

turns out rolling back the django-storages library to 1.14.5 fixes the issue, not sure what changed

[martey]

@HitLuca Do you mean you are seeing this issue with 1.14.6 (not 1.4.6) and that it is not happening with 1.14.5? If so, I can confirm that I am seeing the same thing.

[HitLuca]

Exactly, I fixed the version numbers

[martey]

I think I know why this is occurring. [TL;DR summary: update google-auth to >=2.26.0]

1.14.6 includes #1427, which imports additional dependencies from google-auth:

    from google import auth
    from google.auth.credentials import TokenState
    from google.auth.transport import requests

TokenState first appears in google-auth 2.26.0, so if you are using a version of google-auth lower than this, the import will fail and give you the cryptic message about not being able to load the GCS bindings.

I have figured out a number of possible solutions:

• We could manually add google-auth >= 2.26.0 as a dependency of django-storages[google].
• We could update the google-cloud-storage dependency of django-storages[google]. Fix: Generate Signed Urls through a service account by providing service_account_email and access_token #1427 updated it to >= 1.36.1, but to ensure that a high enough level of google-auth is installed, we would need to update this to >= 2.15.0.
• Because TokenState is an Enum and django-storages is only currently using TokenState.FRESH, we could just hardcode that value and avoid importing TokenState completely.

I personally prefer the last solution for its simplicity (and the fact that it is the least likely to cause additional issues), but will defer to the project maintainer. I think it would also be best to move the google-auth imports into a separate try..except statement, so that any import failure error message does not reference the Google Cloud Storage bindings.

I am willing and able to create a pull request to fix all of this.