feat(pip-compile): support tool version constraints with uv

[maxbrunet]

Changes

• Extract Python version constraint from uv's --python-version flag
• Support uv tool constraint from config

Context

Follow up to #33952 (comment)

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Shouldn't you still fall back to this if python version is missing from the args?

[maxbrunet]

That would not be useful since uv does not write the Python version to the header. If the user does not specify the version with --python-version, uv's behavior is to use the latest version available in the environment

[viceice]

does it prefer config constraints from user config?

[zanieb]

@viceice can you clarify what you mean by that?

[maxbrunet]

I want to say, yes, but I'm not clear on what you mean either

[secustor]

He is referring to what does take priority? The python version extracted from the package file or user configuration in renovate.json

[maxbrunet]

If so, yes, it prefers the value in renovate.json over the extracted value, I have not changed this part of the code:

renovate/lib/modules/manager/pip-compile/common.ts

Lines 18 to 36 in 4e48b5f

	export function getPythonVersionConstraint(
	config: UpdateArtifactsConfig,
	extractedPythonVersion: string | undefined,
	): string | undefined | null {
	const { constraints = {} } = config;
	const { python } = constraints;
	if (python) {
	logger.debug('Using python constraint from config');
	return python;
	}
	if (extractedPythonVersion) {
	logger.debug('Using python constraint extracted from the lock file');
	return `==${extractedPythonVersion}`;
	}
	return undefined;
	}