When using --no-sources
it seems that uv still reads some metadata from workspace packages
#10999
Labels
bug
Something isn't working
Summary
It's related to #10991 - I found it after I tried to make Airlfow workspaces tick.
The problem is that even if
--no-sources
correctly uses actually released packaged inpypi
instead of locally installed packages, some metadata still leaks to theuv pip install
command,In airflow: we have
However I wanted to use local project to install airflow (non-editable) from sources and specific version of the openlineage provider from pypi (2.0.0).
Our provider in PyPI is released (version 2.0.0):
https://pypi.org/project/apache-airflow-providers-openlineage/2.0.0/
One of it's required dependencies is
apache-airflow-providers-common-compat>=1.3.0
In our repo however, in the workspace package we already made the provider dependds on
apache-airflow-providers-common-compat>=1.4.0
- in preparation for the upcoming release. We do not yet whether it is going to be openlineage provider 2.1.0 or 3.0.0 - depending whether it will have some breaking changes, but we already know that it needs common.compat >= 1.4.0. So whilecommon.compat>=1.4.0
is already updated, the pyproject.toml of the provider stil has2.0.0
version set - it will be bumped by the release manager at the release time:https://github.com/apache/airflow/blob/f6b05fe243c17ffb80a4d2497fa7849f27ea507e/providers/openlineage/pyproject.toml#L60
The problem is that this
common.compat >= 1.4.0
and possibly other metadata leaks from the local workspace when--no-sources
is used.Running command:
I get this error:
Seems like the
common-compat>=1.4.0
comes from local workspace version of the package and not fromPyPI
2.0.0 version.Platform
Ubuntu 22.04
Version
0.5.24
Python version
3.9.21
The text was updated successfully, but these errors were encountered: