The current pandas<2.4.0 pin in ibm-watsonx-ai prevents it from being used alongside libraries that require pandas>=3.0.
Current state: ibm-watsonx-ai==1.5.5 requires pandas<2.4.0,>=0.24.2
Problem: pandas 3.0 has been released, and an increasing number of libraries now require pandas>=3.0. This creates unresolvable dependency conflicts in projects that use both ibm-watsonx-ai and any pandas-3-dependent library. For example, in a uv workspace with multiple packages, the resolver cannot find a valid solution when one member depends on ibm-watsonx-ai and another requires pandas>=3.0.1.
This is a continuation of #3, which was closed after the pin was relaxed from <2.3.0 to <2.4.0. The upper bound still needs to be raised to accommodate pandas 3.x.
Request: Test against and support pandas>=3.0, ideally relaxing the constraint to pandas>=0.24.2,<4.0.0 or similar.
The current
pandas<2.4.0pin inibm-watsonx-aiprevents it from being used alongside libraries that requirepandas>=3.0.Current state:
ibm-watsonx-ai==1.5.5requirespandas<2.4.0,>=0.24.2Problem: pandas 3.0 has been released, and an increasing number of libraries now require
pandas>=3.0. This creates unresolvable dependency conflicts in projects that use bothibm-watsonx-aiand any pandas-3-dependent library. For example, in a uv workspace with multiple packages, the resolver cannot find a valid solution when one member depends onibm-watsonx-aiand another requirespandas>=3.0.1.This is a continuation of #3, which was closed after the pin was relaxed from
<2.3.0to<2.4.0. The upper bound still needs to be raised to accommodate pandas 3.x.Request: Test against and support
pandas>=3.0, ideally relaxing the constraint topandas>=0.24.2,<4.0.0or similar.