thclark commented on issue #21019: URL: https://github.com/apache/beam/issues/21019#issuecomment-1183069783
Yeah, it's really necessary that dependencies are updated; it makes it nearly impossible to do anything with current versions of google libraries, being blocked by installation of dependencies that aren't even used in the actual install, only in test. As a simple step to mitigation, the test dependencies could be split into a separate section (e.g. `gcp-test`) to only get installed when actually testing beam, and not throw a spanner in the works when installing it. My current workaround is to not install `apache-beam[gcp]` and just to install `apache-beam`, then manually install the gcp dependencies myself, thereby avoiding the infinite install [in this closely related issue](https://github.com/apache/beam/issues/22218) by pinning dependencies. It's a real pain to do that though. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
