search

scipp / copier_template

Copier template for Scipp projects
BSD 3-Clause "New" or "Revised" License
2 stars 1 forks source link

Use `pip-compile-multi` option `--autoresolve` #106

Closed nvaytet closed 7 months ago

nvaytet commented 7 months ago

We use the --autoresolve option of pip-compile-multi to make sure we don't run into conflicts across multiple txt files.

According to the docs:

This feature works only if your project has a single requirements file, that references (directly or indirectly) all other files.

So I added the all.in file.

TBH, I don't really understand why this is needed, I thought the whole point of pip-compile-multi was to make sure that the versions were the same for all envs, but anyway.

nvaytet commented 7 months ago

It seems that virtualenv now supports platformdirs4 (see https://github.com/pypa/virtualenv/pull/2664), so it now resolves fine without pinning to <3.

The issue with prompt-toolkit remains, but gets resolved by --autoresolve.

nvaytet commented 7 months ago

@jl-wynen this doesn't work with the nightly.in files. It will then use e.g. scipp @ https://github.com/scipp/scipp/releases/download/nightly/scipp-nightly-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl in all .txt files.

So I think we need to go back to pinning the prompt-toolkit version :-(