Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pypy3 does not install latest #296

Closed
2 of 5 tasks
avylove opened this issue Dec 11, 2021 · 2 comments
Closed
2 of 5 tasks

pypy3 does not install latest #296

avylove opened this issue Dec 11, 2021 · 2 comments
Labels
question Further information is requested

Comments

@avylove
Copy link

avylove commented Dec 11, 2021

Description:
I want to use the latest stable pypy release for 3.x. I didn't see a way to do this in the docs, but the action did accept pypy3, however this installs 3.6.12, which looks like the latest version of 3.6 in versions.json.

If there is another way to use the latest version of 3.x, please let me know. I think this is a bug either way, as it is intuitive and accepted, yet doesn't provide intuitive behavior.

Action version:
actions/setup-python@v2

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
pypy3.x

Repro steps:
You can see in this workflow, under the pypy3 job.

matrix.python-version is set to pypy3

  - name: Set up Python ${{ matrix.python-version }}
    uses: actions/setup-python@v2
    with:
      python-version: ${{ matrix.python-version }}

Expected behavior:
The latest stable version supporting Python 3.x should be installed

Actual behavior:
pypy3.6 (3.6.12) is installed

@avylove avylove added bug Something isn't working needs triage labels Dec 11, 2021
@nikita-bykov nikita-bykov added question Further information is requested and removed bug Something isn't working needs triage labels Dec 15, 2021
@nikita-bykov
Copy link
Contributor

Hello @avylove!
pypy3 is old syntax and points only to 3.6 (more information you can find in this PR). You have to specify the PyPy version as stated in the documentation.
For example pypy-3.8 if you want to use the latest release for now.
I'm going to close the issue, but feel free to contact us if you have any questions.

@avylove
Copy link
Author

avylove commented Dec 15, 2021

I'm sorry, but this still seems like a bug. The behavior is not mentioned in the documentation, does not produce a deprecation warning, and does not behave as one would expect. I think there are a few options to remediate:

1.) Print a deprecation warning and plan to retire old behavior
2.) Make pypy3 point to latest 3.x version

In the very least, the behavior should be documented with the other options.

I'll put in a separate feature request to specify the latest 3.x behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants