You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem where I use google-api-python-client V2 which this library does not yet support :-)
Please update it so it can be used with V2 of google-api-python client
Because google-cloud-profiler (3.0.3) depends on google-api-python-client (<1.12.0 || >1.12.0,<2)
and no versions of google-cloud-profiler match >3.0.3,<4.0.0, google-cloud-profiler (>=3.0.3,<4.0.0) requires google-api-python-client (<1.12.0 || >1.12.0,<2).
So, because project-name depends on both google-api-python-client (^2.2.0) and google-cloud-profiler (^3.0.3), version solving failed.
`
The text was updated successfully, but these errors were encountered:
Thanks for reporting the issue! We are aware of this dependency version restriction. The reason for not using client library V2 was an incompatibility issue: googleapis/google-api-python-client#1225. Now that the issue is resolved by googleapis/google-api-python-client#1261, we should be able to get a new version of the Cloud Profiler out to use client library V2.1.0+.
I will update here when a new version is released. Ideally before end of the week, if not, definitely next week. Thanks for your patience!
Hi
I have a problem where I use google-api-python-client V2 which this library does not yet support :-)
Please update it so it can be used with V2 of google-api-python client
`
Updating dependencies
Resolving dependencies... (0.0s)
SolverProblemError
Because google-cloud-profiler (3.0.3) depends on google-api-python-client (<1.12.0 || >1.12.0,<2)
and no versions of google-cloud-profiler match >3.0.3,<4.0.0, google-cloud-profiler (>=3.0.3,<4.0.0) requires google-api-python-client (<1.12.0 || >1.12.0,<2).
So, because project-name depends on both google-api-python-client (^2.2.0) and google-cloud-profiler (^3.0.3), version solving failed.
`
The text was updated successfully, but these errors were encountered: