You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
At the moment the python-version output for PyPy only includes the PyPy release version. In our workflow we use the python-version output to calculate a custom cache key. This breaks if the output for different minor version is the same. PyPy itself uses a combination of python version and internal version to identify each release.
It would be great if the output could be adjusted to include the python version as well. For it's own caching key, the action already uses a combine version identifier.
Uh oh!
There was an error while loading. Please reload this page.
Description:
At the moment the
python-version
output for PyPy only includes the PyPy release version. In our workflow we use thepython-version
output to calculate a custom cache key. This breaks if the output for different minor version is the same. PyPy itself uses a combination of python version and internal version to identify each release.python-version
outputsetup-python/src/find-pypy.ts
Line 99 in a26af69
It would be great if the output could be adjusted to include the python version as well. For it's own caching key, the action already uses a combine version identifier.
setup-python/src/setup-python.ts
Line 111 in a26af69
--
AFAICT this also affects
graalpy
. In that case it isn't an issue though as a particular release only supports one minor python version.Expected behavior:
The
python-version
output for PyPy contains both the fully resolved python version as well as the resolved PyPy version. E.g.`pypy${resolvedPythonVersion}-${resolvedPyPyVersion}`
Actual behavior:
Action version:
v5.6.0
Platform:
Runner type:
Tools version:
PyPy
Repro steps:
Footnotes
https://downloads.python.org/pypy/versions.json ↩
The text was updated successfully, but these errors were encountered: