Prevent pip-compile showing absolute constraint paths #2196
Conversation
If the --constraints path is included in a requirements.*.in file, the absolute path is shown in the comments in the requirements.*.txt output. This appears to be related to a pip upgrade. Specifying the --constraints path as a command line arg instead results in the expected relative paths. We can likely change back when this issue is addressed: jazzband/pip-tools#2131
Deploying databuilder-docs with
|
| Latest commit: |
26ed519
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e466e86e.databuilder.pages.dev |
| Branch Preview URL: | https://compile-reqs.databuilder.pages.dev |
There was a problem hiding this comment.
Have approved, but I am not 100% sure this change is worth it or not.
Having the absolute path is not great, but it's not really a big problem, and as you point out, will probably be fixed.
However, I think including the constraints in the .txt is cleaner than having to pass them.
But then again, we may switch to uv soonish, which will make this all moot.
|
@bloodearnest Yeah, on second thoughts I'm not sure if it's worth it either. Shall we just leave it with the absolute paths and assume it'll go back to the way it was at some point? Also means if you run just pip-compile on its own, you need to remember to pass the constraints path Also no idea why coverage has decided that a line is no longer covered on this PR |
If the --constraints path is included in a requirements..in file, the absolute path is shown in the comments in the requirements..txt output. This appears to be related to a pip upgrade. Specifying the --constraints path as a command line arg instead results in the expected relative paths.
We can likely change back when this issue is addressed: jazzband/pip-tools#2131