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

Restore PyPy2 tests on GitHub Actions #5

Merged
merged 6 commits into from
Dec 11, 2022
Merged

Restore PyPy2 tests on GitHub Actions #5

merged 6 commits into from
Dec 11, 2022

Conversation

mgedmin
Copy link
Owner

@mgedmin mgedmin commented Dec 11, 2022

Because check-python-versions complains and I think it's right.

Let's see if pypy2 is available under a different name maybe?

@mgedmin mgedmin changed the title WIP: restore PyPy2 tests on GitHub Actions Restore PyPy2 tests on GitHub Actions Dec 11, 2022
@mgedmin
Copy link
Owner Author

mgedmin commented Dec 11, 2022

https://github.com/actions/setup-python/releases/ says the legacy names 'pypy2' and 'pypy3' were removed in v3 (back in February); v4 allows (and recommends) using 'pypy2.7'/'pypy3.8' instead of 'pypy-2.7'/'pypy-3.8'.

I was still using v2. Not sure why it broke. Not sure I care, this is an opportunity to upgrade to v4.

I also looked into using setup-python's builtin pip cache support, but I don't understand how it works. I don't have a requirements.txt, just a list of packages. And then there's tox where each toxenv has its own dependencies. I assume setup-python would know how to distinguish caches by python version, but there's no way I could find to tell it to use separate caches for separate toxenvs.

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

Successfully merging this pull request may close these issues.

None yet

1 participant