Damian Shaw

> The absolute best thing one can do is write [scenarios](https://github.com/zanieb/packse/blob/main/scenarios/example.json) reproducing the problem so we can a clear statement of the problem and test coverage for the solution. Yeah,...

> `echo "apache-airflow[all]" | uv pip compile - --only-binary apache-beam` resolves I just assumed this was true, but I tried it right now and it didn't resolve for me: ```...

> I just assumed this was true, but I tried it right now and it didn't resolve for me: > > ``` > $ echo "apache-airflow[all]" | uv pip compile...

> I've implemented to specifically target the slow resolution and installation from `pip`. Btw, do you know if any of those optimizations are still required for pip? Or if you've...

> What is left from the "resolution helper" is the list of dependencies i add to address the `--eager upgrade` https://github.com/apache/airflow/blob/main/Dockerfile.ci#L1289 - currently Well uv can certainly suffer from the...

FYI, the error output is different now, but the issue of uv backtracking too far back on apache-beam for Python 3.11 with latest version of airflow still exists as of...

> Our pacakage selection heuristic is currently just going through packages in order we first see them in the requirements of another package - There's definitely room for improvement. Is...

@konstin sorry I don't understand why you've closed this issue: 1. As far as I can tell the root cause has not been determined, I don't agree it was the...

> Haven't been paying close attention to this issue but this heuristic has some downsides. For one, the output resolution for a given set of inputs could change despite no...

> I mean, it's definitely true that changing the order in which you visit packages will change the output resolution in some cases. That's true, but I think the word...