Closed ray-ray closed 1 year ago
As a workaround, I having pinned pyparsing
in my requirements.txt
:
pyparsing==2.4.7
Thanks for reporting this. Looks like the root cause is being tracked here.
We can possibly add some workaround in cloud-profiler-python
while waiting for that to be resolved.
I'm currently occupied with other tasks, but I'll do my best to take a look at this in 1-2 weeks. If your workaround starts breaking badly, please let us know.
I think this is fixed in httplib 0.20.2 (https://github.com/httplib2/httplib2/issues/207#issuecomment-957159308). I was able to import googlecloudprofiler successfully after installing google-cloud-profiler in a clean virtualenv.
Recording versions for posterity:
$ pip freeze
cachetools==5.2.0
certifi==2022.9.24
charset-normalizer==2.1.1
google-api-core==2.10.1
google-api-python-client==2.63.0
google-auth==2.12.0
google-auth-httplib2==0.1.0
google-cloud-profiler==4.0.0
googleapis-common-protos==1.56.4
httplib2==0.20.4
idna==3.4
protobuf==4.21.6
pyasn1==0.4.8
pyasn1-modules==0.2.8
pyparsing==3.0.9
requests==2.28.1
rsa==4.9
six==1.16.0
uritemplate==4.1.1
urllib3==1.26.12
Starting today, when I
import googlecloudprofiler
, I get this traceback;Looks like the latest
pyparsing
release changed the name of these functions: https://pyparsing-docs.readthedocs.io/en/latest/whats_new_in_3_0_0.html#other-discontinued-features