[manager/pip-compile] Contstraint used pip version #39226
Unanswered
Shegox
asked this question in
Request Help
Replies: 1 comment
-
|
The new version |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
Which platform you running Renovate on?
GitHub Enterprise Server
Which version of Renovate are you using?
41.169.3
Please tell us more about your question or problem
All current
pip-compile(<=7.5.1) versions are incompatible with the latestpipversion (25.3) (see jazzband/pip-tools#2252).Inside the Renovate container, Renovate dynamically installs
pythonandpip-compile.pipis installed as a side-affect of thepythoninstall. It seems that currently the latest pip version is always installed (25.3). Forpip-compileto work however we would need to forcepip<25.3.Currently this causes
pip-compilejobs to fail with this error:Specifiying a custom constraint for
pipdoesn't have any affect. Specificying a constraint forpythonallows to set a lower older python version (e.g.3.10.0), however it seems that latestpipis still installed:Is there a way currently to control/constrain the used
pipversion in combination withpip-compile? From my investigation of thepip-compilemanager it doesn't seem so.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions