pypy3.11 under GitHub Actions's windows-latest fails to install pylint≥3.3.5

[aaronliu0130]

Bug description

# In dev requirements:
pylint>=3.3.5

Configuration

Command used

pip install -e .[dev]

Pylint output

INFO: pip is looking at multiple versions of cpplint[dev] to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement pylint>=3.3.5; extra == "dev" (from cpplint[dev]) (from versions: 0.15.2, 0.16.0, 0.18.0, 0.18.1, 0.19.0, 0.20.0, 0.21.0, 0.21.1, 0.21.2, 0.21.3, 0.22.0, 0.23.0, 0.24.0, 0.25.0, 0.25.1, 0.25.2, 0.26.0, 0.27.0, 0.28.0, 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.3.1, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 2.0.0.dev0, 2.0.0.dev1, 2.0.0.dev2, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0.dev0, 2.3.0.dev1, 2.3.0.dev2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.7.0.dev1, 2.7.0, 2.7.1.dev1, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0, 2.8.1.dev1, 2.8.1, 2.8.2, 2.8.3, 2.9.0.dev1, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.4, 2.9.5, 2.9.6, 2.10.0, 2.10.1, 2.10.2, 2.11.0, 2.11.1, 2.12.0, 2.12.1, 2.12.2, 2.13.0, 2.13.1, 2.13.2, 2.13.3, 2.13.4, 2.13.5, 2.13.6, 2.13.7, 2.13.8, 2.13.9, 2.14.0b1, 2.14.0, 2.14.1, 2.14.2, 2.14.3, 2.14.4, 2.14.5, 2.15.0, 2.15.2, 2.15.3, 2.15.4, 2.15.5, 2.15.6, 2.15.7, 2.15.8, 2.15.9, 2.15.10, 2.16.0.dev0, 2.16.0b0, 2.16.0b1, 2.16.0, 2.16.1, 2.16.2, 2.16.3, 2.16.4, 2.17.0, 2.17.1, 2.17.2, 2.17.3, 2.17.4, 2.17.5, 2.17.6, 2.17.7, 3.0.0a0, 3.0.0a1, 3.0.0a3, 3.0.0a4, 3.0.0a5, 3.0.0a6, 3.0.0a7, 3.0.0b0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.1.1, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4)
ERROR: No matching distribution found for pylint>=3.3.5; extra == "dev"
Error: Process completed with exit code 1.

Expected behavior

It would install 3.3.5

Pylint version

N/A

OS / Environment

Current runner version: '2.323.0'
Operating System
Microsoft Windows Server 2022
10.0.20348
Datacenter
Runner Image
Image: windows-2022
Version: 20250330.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20250330.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20250330.1
Runner Image Provisioner
2.0.422.1

Full runner logs seen at https://github.com/cpplint/cpplint/actions/runs/14233489310/job/39888515167?pr=334

Additional dependencies

[aaronliu0130]

Linking cpplint/cpplint#334, where we discovered this problem

[Pierre-Sassoulas]

It seems there's a typo in your requirements: pylint>=3.35 should be pylint>=3.3.5

[aaronliu0130]

@Pierre-Sassoulas Apologies, but that was only a typo in filling this issue. Our actual requirements at https://github.com/cpplint/cpplint/pull/334/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R45 correctly say 3.3.5, and the logs under the "Pylint output" section also correctly say 3.3.5. It says ERROR: No matching distribution found for pylint>=3.3.5.

[Pierre-Sassoulas]

Maybe due to a transitive dependency in windows ( "colorama>=0.4.5; sys_platform=='win32'",) not being available ? I can't check, I'm on mobile. Otherwise I don't think using pypy makes a difference metadata wise so I don't know what could be wrong (pip doesn't say what is not matching for 3.3.6 in the log).

[aaronliu0130]

Successfully installed astroid-3.3.9 colorama-0.4.6 dill-0.3.9 isort-6.0.1 mccabe-0.7.0 platformdirs-4.3.7 pylint-3.3.6 tomlkit-0.13.2

There's no problem installing pylint under pypy3.11 on my (emulated) Windows machine (logs above); the problem just mysteriously appears in GitHub Actions.

[Pierre-Sassoulas]

Sound like a hard to troubleshoot problem involving github actions and or pypi, and not pylint directly, what do you think ?

[aaronliu0130]

Would there be a better place to ask this? The GitHub community discussions forum is kinda dead. Some ways to troubleshoot would also be nice.

[Pierre-Sassoulas]

Does it happens frequently ? If so it might be a caching issue in your action. Because if was a cache issue with pypi, it would have been caught if it was frequent (and if it's rare then it's probably easier to hit refresh than to fill an issue with the pypi team with enough details for it to be actionnable).

[aaronliu0130]

It always happens. It happened for every run in that PR across weeks.

[Pierre-Sassoulas]

This strongly suggest a problem with the github action and not pypi/pylint, so I'm going to close, but good luck with the debugging :)