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 nanobind-bazel v2.0.0 #2127

Merged
merged 1 commit into from
May 28, 2024
Merged

Conversation

nicholasjng
Copy link
Contributor

Provides capabilities for building Python bindings with Bazel using nanobind v2.0.0, which was released recently.

@nicholasjng nicholasjng force-pushed the add-nanobind-bazel-v2 branch from f18603d to 16e1b50 Compare May 27, 2024 08:32
@nicholasjng
Copy link
Contributor Author

This is to enable moving forward on google/benchmark#1790.

@nicholasjng nicholasjng force-pushed the add-nanobind-bazel-v2 branch from 16e1b50 to bebc021 Compare May 28, 2024 11:20
@nicholasjng
Copy link
Contributor Author

I restored the compatibility level back to 1, I'm guessing that build failures because of the underlying nanobind changes are hint enough that old versions need to be upgraded.

Provides capabilities for building Python bindings with Bazel
using nanobind v2.0.0, which was released recently.
@nicholasjng nicholasjng force-pushed the add-nanobind-bazel-v2 branch from bebc021 to 216d95f Compare May 28, 2024 17:04
@fmeum fmeum merged commit b8852e7 into bazelbuild:main May 28, 2024
18 checks passed
aiuto pushed a commit to aiuto/bazel-central-registry that referenced this pull request Jun 3, 2024
Provides capabilities for building Python bindings with Bazel using
nanobind v2.0.0, which was released recently.
zaucy pushed a commit to zaucy/bazel-central-registry that referenced this pull request Jun 14, 2024
Provides capabilities for building Python bindings with Bazel using
nanobind v2.0.0, which was released recently.
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.

2 participants