-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
Windows and Mac testing #4
Comments
@ManifoldFR you might want to try this for point-process-rust |
Created a test branch here.
Seems like I'm running into this error. Do I need to install any additional tooling to make it work on macOS? |
Oh well, it shouldn't check for manylinux compliancy on mac 😅 I've fixed it in e6a2de8.
Yes, pyo3-pack is zero configuration and needs only a rust crate. Now that you already have a setuptools configuration it's imho a good idea to keep it as pyo3-pack won't be able to build source distribution for a while (those get compiled when installed, so package can be installed on python versions and platforms for which there are no wheels. The culprit in this case is pip though. See #2) I've tried to make this a bit clearer in the readme. |
After your fix it works!
Thanks for that! I guess we can use it to publish hyperjson on pypi. |
Nice to hear in works on mac! You don't need to do anything manylinux-related. pyo3-pack includes an auditwheel reimplementation and checks your libraries for compliance automatically. |
pyo3-pack is meant as a replacement for setuptools-rust and is as such feature complete. As I'm working primarily on linux, I did only very limited tests on windows and don't have any mac to test on. It'd appreciate help testing those platforms.
To install pyo3-pack, you can use a prebuilt binary or
cargo install pyo3-pack
. For testing you can take any pyo3-powered python extension (e.g. hyperjson, pyo3's example or rust-numpy's example), build it, install it with pip and check if you can import it. I'd also be interested in feedback on the user experience (e.g. incomprehensible error message that showed up).CC @althonos @mre @fafhrd91
The text was updated successfully, but these errors were encountered: