Currently, `urllib3` is pinned: https://github.com/databricks/databricks-cli/blob/dd47ce4b42cd3ad17fc74022651aa0dbbbaf1d98/setup.py#L45 This happened in https://github.com/databricks/databricks-cli/pull/637. Is this pin (still) necessary? The PR description makes it sound like we needed this pin for `requests`. But `requests` should be fine with `urllib3<3`, see [here](https://github.com/psf/requests/blob/6e5b15d542a4e85945fd72066bb6cecbc3a82191/setup.py#L64). This caused some hiccups on the conda packaging side (where the pin was missing), see https://github.com/conda-forge/databricks-cli-feedstock/pull/23.
Currently,
urllib3is pinned:databricks-cli/setup.py
Line 45 in dd47ce4
This happened in #637. Is this pin (still) necessary?
The PR description makes it sound like we needed this pin for
requests. Butrequestsshould be fine withurllib3<3, see here.This caused some hiccups on the conda packaging side (where the pin was missing), see conda-forge/databricks-cli-feedstock#23.