Summary

We use uv pip compile to provide a constraints file for reproducible builds and testing (even for pip install).

Most recent release of napari-plugin-manager added a napari as a dependency, where napari depends on napari-plugin-manager.

So when we run uv pip compile on the napari project (pyproject.toml)
https://github.com/napari/napari/blob/e8abcaf5fea49e872b07a998f1a3bcde628dee80/.github/workflows/upgrade_test_constraints.yml#L168

It ends with adding napari==0.6.6 to the constraints file. napari/napari@86ea147#diff-347d546af1ecc381608b9b2a5635a7daeb1a4740c6db0550e39fe735da7e79dbR246

Could I request not to include the constraints in the package, which pyproject.toml is input to uv pip compile? And especially do not use constraints of the released version when calculating compile output.

Sometimes, cyclic dependencies are not possible to avoid (we will try to work around it).

Platform

linux GHA

Version

0.9.4

Python version

3.12.12