Another magic pip resolver hint

[notatallshaw]

See #53306 and CC: @potiuk

The issue is many versions (e.g. 1.33.0) of snowflake-snowpark-python require protobuf<6,>=3.20 but this conflicts largely with grpcio-status where many versions (e.g. 1.73.1) require protobuf<7.0.0,>=6.30.0.

This takes advantage of the fact that pip uses an upper bound as an indicator that that requirement must be resolved first, without adding any actual restrictions on upper bounds: https://pip.pypa.io/en/stable/topics/more-dependency-resolution/#the-resolver-algorithm

Unfortunately this particular one trips up even the optimistic back tracker optimization coming in pip 25.2, so either I need to figure out some more optimizations for pip's resolver to handle this, or pip needs a whole new resolver.

[gopidesupavan]

cool @notatallshaw thanks :)

[gopidesupavan]

let me close and reopen PR with full tests

[gopidesupavan]

Triggered with full tests.

[potiuk]

Oh. Cool. Let's just merge it - currently the "push" step will not happen even if we do full tests - it is only run in canary builds and that requires maintainer to run PR from Airflow repo.

[potiuk]

Thanks a lot @notatallshaw !. I am triggering canary build now.

[bugraoz93]

Thanks a lot @notatallshaw !

[gopidesupavan]

Nice the magic worked 😄

[potiuk]

thanks @notatallshaw !