Integration testing: Install latest / nightly wheels

[jl-wynen]

This is about the integration testing repo. But I want to track it in a way that we don't forget too easily.

Currently, we lock dependencies using pip-compile. But we don't want to lock our own packages but install the latest version instead. We achieve this by manually removing the pins from those packages in requirements/*.txt files. This is not sustainable.

We can fix this by using the nightly wheels in the *.in files.

Downside: The locked dependencies and dependencies of the nightly wheels are not synced. So we may end up with broken envs. But this is already the case with our scipp-internal nightly envs.

[SimonHeybrock]

Currently, we lock dependencies using pip-compile. But we don't want to lock our own packages but install the latest version instead. We achieve this by manually removing the pins from those packages in requirements/*.txt files. This is not sustainable.

Are we doing that? I was not aware? Or are you referring to the pip-compile in the integration testing repo, not the one here?

[jl-wynen]

Yes, the integration testing repo. Sorry for being unclear.