tracebacks on connect from discovery_cache - "ModuleNotFoundError: No module named 'google'" on 18.04/bionic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-googleapi (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
With python3-googleapi 1.5.5-1 installed on ubuntu 18.04 bionic system we get several tracebacks on connect/discovery related to discovery_cache and module load:
Traceback (most recent call last):
File "/usr/lib/
from google.
ModuleNotFoundE
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
from oauth2client.
ModuleNotFoundE
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
from oauth2client.
ModuleNotFoundE
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
from . import file_cache
File "/usr/lib/
'file_cache is unavailable when using oauth2client >= 4.0.0')
ImportError: file_cache is unavailable when using oauth2client >= 4.0.0
On bionic exhibiting the above behavior the versions of the api client and oauth2 libs are:
log-archive@
ii python3-googleapi 1.5.5-1 all Google APIs Client Library - Python 3.x
log-archive@
ii python3-
ii python3-oauthlib 2.0.6-1 all generic, spec-compliant implementation of OAuth for Python3
This does not occur on a 16.04/xenial system running python3-googleapi version 1.4.2-1ubuntu1.1
It also does not occur on artful which is also 1.5.5-1 but with earlier oauth2client:
log-archive@
ii python3-googleapi 1.5.5-1 all Google APIs Client Library - Python 3.x
log-archive@
ii python3-
ii python3-oauthlib 2.0.1-1