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

Support for python 3.11 #704

Merged
merged 17 commits into from
Apr 18, 2023
Merged

Conversation

ayys
Copy link
Member

@ayys ayys commented Apr 5, 2023

This PR is to make wasmer-python run with support for python 3.11

I also wanted to get wasmer-python working on M1 as well, but could not get llvm to compile. That should probably be a separate PR anyway since this one is fixing too many things already.

@ayys ayys force-pushed the run-on-m1-with-python-3.11 branch 2 times, most recently from 76d793b to da52536 Compare April 11, 2023 10:28
@ayys ayys changed the title Run on m1 with python 3.11 Support for python 3.11 Apr 11, 2023
- Adds python 3.11 to Cargo.toml files
- Adds tests for python 3.11 in CI
@ayys ayys force-pushed the run-on-m1-with-python-3.11 branch from da52536 to af35692 Compare April 11, 2023 10:30
Copy link

@Michael-F-Bryan Michael-F-Bryan left a comment

Choose a reason for hiding this comment

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

Keep in mind that this means we'll forever need to keep Cargo.toml and pyproject.toml in sync. I'd much prefer to use just Cargo.toml instead of a mixture of Cargo.toml and pyproject.toml, and let maturin generate the pyproject.toml.

Release tools like cargo release won't know to bump version numbers in both Cargo.toml and pyproject.toml, so we'll need to keep version numbers in sync manually.

Comment on lines 1 to 38
[project]
name = "wasmer"
version = "1.1.0"
description = "Python extension to run WebAssembly binaries"
readme = "README.md"
repository = "https://github.com/wasmerio/wasmer-python"
keywords = ["python", "extension", "webassembly"]
categories = ["wasm"]
build = "build.rs"

[package]
edition = "2018"

[build-system]
requires = ["maturin>=0.14,<0.15"]
build-backend = "maturin"

[tool.maturin.metadata]
category = ["Programming Language :: Python",
"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
"Programming Language :: Python :: Implementation :: CPython",
"Programming Language :: Rust",
"Topic :: Software Development",
"Topic :: Software Development :: Compilers",
"Topic :: Software Development :: Interpreters",
"License :: OSI Approved :: MIT License",
"Operating System :: OS Independent"]


[tool.maturin.project-url]
"Source Code" = "https://github.com/wasmerio/wasmer-python/"
"Bug Tracker" = "https://github.com/wasmerio/wasmer-python/issues"
"Documentation" = "https://github.com/wasmerio/wasmer-python/"

Choose a reason for hiding this comment

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

Keep in mind that this means we'll forever need to keep Cargo.toml and pyproject.toml in sync. I'd much prefer things like keywords, version number, description, and so on are specified in Cargo.toml so we only need to manage one file per package.

This also makes releases more annoying because release tools like cargo release won't know to update the version number in both files.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've this this issue by removing the project section from pyproject.toml. This means the version will only need to be updated in Cargo.toml.

@Michael-F-Bryan
Copy link

@ayys will this fix #715, #696, #680, and #657? If so, can you update the PR's description so those tickets will be closed when this merges?

@ayys
Copy link
Member Author

ayys commented Apr 14, 2023

I've upadted the description with the issues. #657 isn't fixed by this PR, but the others are.

@ayys ayys merged commit bf419ad into wasmerio:master Apr 18, 2023
@ninoseki
Copy link

Hello, first of all, thank you for the great work!
Can I ask why v1.1.1 (the latest version includes this change) is still not published in PyPI?

@ninoseki
Copy link

@ayys @Michael-F-Bryan Sorry for bothering but I'd appreciate if you could check my question.

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.

3 participants