notatallshaw commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2040164554
> Agree. `uv` has the big advntage for now that it does not `have` to support all those legacy cases - far less number of people will complain if something won't work :) Well, `uv` is trying to capture the existing Python ecosystem, which means they are making choices to support a wider range of things rather than follow the spec. You can see here all the "fixups" they do to specifiers: https://github.com/astral-sh/uv/blob/c4107f9c40b58cea629b6a7b6e59663d30f96f41/crates/pypi-types/src/lenient_requirement.rs#L11-L57 And since they've been public I've seen users report several times on bad specifiers they rely on and I've seen uv add them to the list of fixups. It's a bit of a shame, but I understand their reasoning. I think it will be up to pip to release a breaking change and force the ecosystem to follow the spec. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
