-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: move to scikit-build-core #48
Conversation
Do you compile a CPython extension, actually? Is they any difference between a cp37 wheel and a cp311 wheel? If not, scikit-build-core supports native production of single pythonless wheels. It also supports expanding all macOS tags from universal. |
no, there's definitely no CPython (or python-binding) going on here. This is basically, cross-compile the files for each platform and ship the |
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>
99362a6
to
fa4eb35
Compare
FYI, don't make a release quite yet, I need to fix the license file location in scikit-build-core 0.4.0. 0.4.1 should fix that. |
scikit-build-core 0.4.1 is out, everything should be fine again. :) |
Trying out scikit-build-core.
This should also fix the missing
py.typed
and_version.pyi
files from the current wheels.See list of improved features at https://github.com/scikit-build/scikit-build-core:
CMAKE_PREFIX_PATH
PyPY SOABI & Limited API / Stable ABI
CMAKE_GENERATOR
build-dir
)soon)
on import
The following limitations are present compared to classic scikit-build: