make pyenv backend respect patch version constraints

[jonasrauber]

fixes #20175

fix inspired by #19462

[huonw]

Thank you for contributing!

The code looks good to me, but I'll loop @thejcannon in too.

Could we add a test to src/python/pants/backend/python/providers/pyenv/rules_integration_test.py that validates that this works (and will continue to in future)?

One option might be evolving the test_using_pyenv test to take two parameters like ("interpreter_constraints", "expected_version_substring"), and then pass ("2.7.*", "2.7"), ("3.9.*", "3.9"), ("3.10.4", "3.10.4") or something like that. What do you think?

pants/src/python/pants/backend/python/providers/pyenv/rules_integration_test.py

Lines 65 to 66 in cfb3caf

	@pytest.mark.parametrize("py_version", ["2.7", "3.9"])
	def test_using_pyenv(rule_runner, py_version):

[jonasrauber]

@huonw Added the test. Pretty much as you described. Also made sure that the test fails without this PR:

E       AssertionError: assert '3.10.4' in '3.10.10 (main, Jul  9 2024, 18:05:03) [Clang 15.0.0 (clang-1500.3.9.4)]'

With the fixes from this PR it passes.

[huonw]

Nice one! I like it.

[huonw]

Ah, I did another skim and thought of a few other things. Sorry about the dribble of reviews!

[huonw]

Ah, on second-review: it'd be good to have a test that validates this logic too, i.e. interpreter constraints that constraint to a patch version that Pyenv doesn't know about (and hopefully will never know about, to avoid spurious failures in future).

[huonw]

Thanks for the contribution @jonasrauber! I've been nitpicky, so I'll fix those minor issues myself rather than force it onto you.