Conversation
The error says: But why would |
|
I don't understand why it's talking about units. I looked a little bit into it, tried to blame to see when it changed. On one side, I'm wondering if it's revealing some edge case in scipp or I looked at the versions: before it was failing, it was installing Now it's installing Note that only plopp has changed. At least it's claiming that:
Because I tried to create an environment with the same versions locally, and I get Only difference is I am using |
|
Maybe plopp did indeed not use this code branch? Anyway, Claude found that this was indeed a bug and fixed in scipp 24.11.0 by 75308cc66 ("fix: make islinspace unit none", PR scipp#3533). Ths changed the element-op unit lambda from units::one to units::none. I suppose you should bump the minimum Scipp version instead of applying this? |
|
Should I think the changes here don't hurt in any case. But I will bump scipp minimum version in scippneutron. |
I understand now what happens: in Plopp's pyproject, we did not include Scipp as a dependency, only in the That is out of date with our pyproject.toml: https://github.com/scipp/plopp/blob/main/pyproject.toml#L40 I think we didn't add scipp in the deps, because Scipp also has plopp as an optional runtime dependency, and we thought we would end up in a circular dependency where plopp needs scipp but scipp needs plopp. Maybe Plopp should just have Scipp as a core dependency? (It's using it internally everywhere) |
|
ChatGPT says:
Then the pip, uv, conda should still happily solve the environments.
|
|
I will close because in the future, if we change |
We add
.valuetosc.islinspace.This was tripping up some builds in Scippneutron: https://github.com/scipp/scippneutron/actions/runs/24816917140/job/72633086173