notatallshaw opened a new pull request, #51742: URL: https://github.com/apache/airflow/pull/51742
Related to https://github.com/apache/airflow/pull/51702. There is a resolution "knot" involving `protobuf` when pip 25.1 attempts to resolve dependencies during CI. Many Google dependencies require `protobuf`, but `grpcio-status` and `opentelemetry-proto` often have conflicting version requirements, for example: * `grpcio-status` 1.73.0 requires `protobuf<7.0.0,>=6.30.0` * `opentelemetry-proto` 1.27.0 requires `protobuf<5.0,>=3.19` Because so many packages depend on `protobuf`, pip's heuristics struggle to correctly identify which packages to backtrack on, leading to resolution too deep errors. This change introduces a workaround by adding `opentelemetry-proto` with an upper bound to the dependency list. This signals to pip that the package should be resolved early, while the use of a very high upper bound ensures that it doesn't meaningfully restrict user environments. I considered using a requirement like `opentelemetry-proto<2!0`, but decided against it, as it felt too magical and might break tools that are not fully PEP 440 compliant. -- 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]
