mirror of https://github.com/astral-sh/uv
In pathological cases, it's hard to follow why the resolution is slow. This is an attempt to give the user an indication what is slow (boto3) and how to fix this (add a manual boto3 constraint). This also helps to determine if this is a pathological case or a server that doesn't support range requests. The values i picked are somewhat arbitrary. ``` $ uv pip install bio_embeddings ⠸ pytest==8.0.2 warning: Downloading metadata for more than 50 different versions of boto3. Consider adding a stricter version constraint for this package to speed up resolution. warning: Downloading metadata for more than 50 different versions of botocore. Consider adding a stricter version constraint for this package to speed up resolution. ⠼ boto3==1.26.85 ``` `warn_user!` interacts badly with the `Reporter`, do we have a way to pause-and-restart the restart the reporter when showing our own messages, similar to tqdm or `IndicatifLayer`? |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||