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

GraalPy support #3148

Closed
kurtmckee opened this issue Nov 1, 2023 · 1 comment
Closed

GraalPy support #3148

kurtmckee opened this issue Nov 1, 2023 · 1 comment

Comments

@kurtmckee
Copy link
Contributor

What's the problem this feature will solve?

The GitHub action actions/setup-python has recently merged a PR to support GraalPy (note that this support hasn't been released yet -- to access it, I think it's still necessary to reference actions/setup-python@main in a CI workflow).

GraalPy will be the third interpreter type available when running jobs in GitHub CI, and I'd like to have a way to test it alongside CPython and PyPy, as a defined tox environment.

Describe the solution you'd like

I'd like to be able to specify GraalPy as a target interpreter for a tox environment.

Their version scheme appears to differ from CPython and PyPy -- in GitHub it's referenced as "graalpy-23.0"...it seems they currently target Python 3.10 as the language version.

Alternative Solutions

I haven't tried anything to resolve this. I imagine (but haven't tested!) that manipulating the $PATH might allow tox to only see the GraalPy python executable.

Additional context

@gaborbernat
Copy link
Member

This sounds like something that should live as a plugin first until gets wide adoption.

@gaborbernat gaborbernat closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants