Zanie Blue

Adding logs to trace where we're at We're stuck here https://github.com/astral-sh/uv/blob/ae1edef9c0a4906cd22838b30fd719723c6cb67e/crates/uv-resolver/src/lock/mod.rs#L265-L276 https://github.com/astral-sh/uv/blob/ae1edef9c0a4906cd22838b30fd719723c6cb67e/crates/uv-resolver/src/lock/mod.rs#L2453-L2462 This `Dependency::from_annotated_dist` does not return. I believe it's this call in `Dependency::new` that's stuck https://github.com/astral-sh/uv/blob/ae1edef9c0a4906cd22838b30fd719723c6cb67e/crates/uv-resolver/src/lock/mod.rs#L4852 It looks like...

I'd highly recommend trimming down the number of conflicts, are all of those packages actually mutually conflicting?

I think it's a problem with processing all the markers that are generated to represent the conflicts.

Docs work is tracked in https://github.com/astral-sh/uv/issues/5200 There was a proposed change adding `uv add -r pyproject.toml` support but it never got finished due to concerns about expectations around what would...

I tried to reproduce this, but could not: ``` ❯ uv init example ❯ cd example ❯ uv add --group old django==4.2.16 Using CPython 3.12.7 Creating virtual environment at: .venv...

Ah actually I'm successful if I add the stubs package ``` ❯ uv add django-stubs==5.1.1 Resolved 15 packages in 277ms Prepared 4 packages in 155ms Installed 5 packages in 694ms...

I believe this is a bug with the same root cause as https://github.com/astral-sh/uv/issues/9289 We're writing ambiguous entries to the lockfile. Will be resolved by a solution like https://github.com/astral-sh/uv/pull/9370

In brief the current recommendation is: - Attempt to merge the parent into your branch, encounter a merge conflict in the lockfile - Checkout the lockfile from the parent `git...

Are you using a dynamic package version or does it just change a lot?

👍 yep that's the issue to track. No problem :)