Fix python dependency installation in CI

[MaEtUgR]

Solved Problem

Solution

Try being less specific following https://peps.python.org/pep-0440/#version-specifiers

Test coverage

Let's see if that works 👀

[MaEtUgR]

ok, at least we know for sure it's not empty version requirement dependent 🦶

[MaEtUgR]

The second commit fixes the problem. I think it's because "setuptools" gets updated by the actions plugin we use but "packaging" is not updated. So I update that one manually just before that. Had the idea after reading pypa/setuptools#4496 (comment) The first commit is not necessary but would allow using patch releases like empty 3.3.5 which will likely not come out but who knows.

[MaEtUgR]

Can't get the other ones to pass but it's intermittent 😠 One CI issue solved, next pr for the next one.

[mrpollo]

Thanks!, I had fixed this here too, #23962

[MaEtUgR]

@mrpollo Good that you had a look as well 👍
I wonder why your pr worked these update flags are true by default. Probably because you changed the container version and probably the version of the packaging package.

I made an upstream pr with my fix: py-actions/py-dependency-install#255
and tested it for us: #24016
Let's see what maintainers say 👀