Zanie Blue
Zanie Blue
Ah yes the resolver needs to solve for all extras in the workspace. Let me check-in with the team to see if we have a recommended workaround.
@danielgafni we've been talking about this quite a bit internally, especially in the context of PEP 735 — I think we'll try to implement something for this in the near...
There's a tracking issue at https://github.com/astral-sh/uv/issues/6981
@danielgafni heads up — we just released support for declaring conflicting extras.
Can you share a diff of the `PYTHON.json` metadata?
Thanks! The change in the metadata makes sense to me but I don't fully understand why it was written this way in the first place?
Thanks for the report. Do you know if Conda builds with any particular performance flags?
I did an actual performance run (Linux x86-64) and it looks like there's a significant difference here ``` ❯ uvx pyperf compare_to conda-forge-313.json pbs-313.json All benchmarks: =============== 2to3: Mean +-...
Looking at https://github.com/conda-forge/python-feedstock/blob/main/recipe/build_base.sh and not seeing anything obvious.
@paugier What platform and architecture did you run your benchmarks on?