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

Add basic support for GraalPy #1645

Merged
merged 2 commits into from Jun 4, 2023
Merged

Conversation

timfel
Copy link
Contributor

@timfel timfel commented Jun 2, 2023

I am working on making PyO3 support GraalPy in https://github.com/timfel/pyo3/tree/timfel/graalpy-support. To run the tests, I noticed I need maturin, so I had to make changes here as well. However, to run the maturin tests, I need the PyO3 changes.

Right now with this PR and my PyO3 branch, I can run the maturin tutorial example and a small number of PyO3 tests. Since the PyO3 changes will grow, whereas I expect the changes here to not be much more, I would like to open this for discussion.

@netlify
Copy link

netlify bot commented Jun 2, 2023

Deploy Preview for maturin-guide ready!

Name Link
🔨 Latest commit 3bd154e
🔍 Latest deploy log https://app.netlify.com/sites/maturin-guide/deploys/647c0457c8a405000850dad6
😎 Deploy Preview https://deploy-preview-1645--maturin-guide.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Member

@konstin konstin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, i'm fine with merging this before pyo3 support is finished, especially if this unblocks you on adding support to pyo3. We already have some targets that are supported but not really tested (similar to tier 3 platform in rust in many ways)

@@ -9,6 +9,7 @@ use std::io::{BufRead, BufReader};
use std::path::Path;

const PYPY_ABI_TAG: &str = "pp73";
const GRAALPY_ABI_TAG: &str = "graalpy230_310_native";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the graalpy abi versioning policy? would be good to have that as a comment somewhere

Comment on lines +24 to +28
# This should probably return the ABI tag based on EXT_SUFFIX in the same
# way as pypa/packaging. See https://github.com/pypa/packaging/pull/607.
# For simplicity, we just fix it up for GraalPy for now and leave the logic
# for the other interpreters untouched, but this should be fixed properly
# down the road.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'd be happy to switch this over to what pypa/packaging does entirely, their logic is authoritative for all other tools anyway

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's tracked here: #1545

@messense messense added the GraalPy GraalPy interpreter label Jun 3, 2023
@messense messense merged commit dcbb65f into PyO3:main Jun 4, 2023
32 checks passed
@timfel timfel deleted the timfel/graalpy-support branch June 20, 2023 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GraalPy GraalPy interpreter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants