[pixi-build] how to tell pixi not to always reinstall a package when running any task depending on it

[kratsg]

Using the pixi-build-python backend, suppose I do something like

[workspace]
channels = ["https://prefix.dev/conda-forge"]
platforms = ["win-64", "linux-64", "osx-arm64", "osx-64"]
preview = ["pixi-build"]

[dependencies]
python_rich = { path = "." }

[tasks]
start = "rich-example-main"

[package]
name = "python_rich"
version = "0.1.0"

[package.build]
backend = { name = "pixi-build-python", version = "==0.4.0" }

[package.host-dependencies]
hatchling = "==1.26.3"

[package.run-dependencies]
rich = "13.9.*"

[feature.test.dependencies]
pytest = ">=9"

[feature.test.tasks]
test = { cmd = "pytest", description = "Run basic pytest tests" }

anytime one runs pixi run pytest -- it always rebuilds the package

$ pixi run pytest

 ╭─ Running build for recipe: python_rich-latest-pyh4616a5c_0
 │
 │ ╭─ Fetching source code
 │ │ No sources to fetch
 │ │
 │ ╰─────────────────── (took 0 seconds)
 │
 │ ╭─ Externally resolved dependencies recipe: python_rich-latest-pyh4616a5c_0
...

which is - from a developer perspective - a little jarring and annoying. I can also see why this might want to be the case, but I imagine having some sort of cache like inputs = ["python_rich/src/python_rich"] would make more sense - because if I am working on writing tests and I am not changing the source code, it's not apparent to me that I would want to reinstall the package when I edit other files within it.

[ruben-arts]

Right now you can use pixi run --as-is when running a task. This will avoid the environment installation completely.

The input globs can be modified by the user through extra-input-globs

I believe you can negate the original inclusion using a "!xxx.py" as extra input glob.

[kratsg]

I see. Do you know what's included in the default globs that triggers a rebuild of the package every time? If there are no changes to any of the source files, it's not clear to me what would have triggered it.