-
Notifications
You must be signed in to change notification settings - Fork 39
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
Update Pybind11 version for NP2.0 compatibility #816
Conversation
Hello. You may have forgotten to update the changelog!
|
[sc-61400] |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #816 +/- ##
===========================================
- Coverage 97.10% 81.86% -15.25%
===========================================
Files 117 17 -100
Lines 18642 1991 -16651
===========================================
- Hits 18103 1630 -16473
+ Misses 539 361 -178 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small PR, but could you update the change log nevertheless?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @mlxd .
Please complete the following checklist when submitting a PR: - [x] All new features must include a unit test. If you've fixed a bug or added code that should be tested, add a test to the [`tests`](../tests) directory! - [x] All new functions and code must be clearly commented and documented. If you do make documentation changes, make sure that the docs build and render correctly by running `make docs`. - [x] Ensure that the test suite passes, by running `make test`. - [x] Add a new entry to the `.github/CHANGELOG.md` file, summarizing the change, and including a link back to the PR. - [x] Ensure that code is properly formatted by running `make format`. When all the above are checked, delete everything above the dashed line and fill in the pull request template. ------------------------------------------------------------------------------------------------------------ **Context:** Pybind11's 2.12 release is the first version to officially support Numpy 2.0. This PR updates Lightning's pybind11 version to ensure compatibility to/from numpy arrays. **Description of the Change:** Updates Pybind11 version to the latest (2.13.5) **Benefits:** Ensures direct compatibility with numpy 2.x **Possible Drawbacks:** None. **Related GitHub Issues:** --------- Co-authored-by: ringo-but-quantum <github-ringo-but-quantum@xanadu.ai>
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests
directory!All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs
.Ensure that the test suite passes, by running
make test
.Add a new entry to the
.github/CHANGELOG.md
file, summarizing thechange, and including a link back to the PR.
Ensure that code is properly formatted by running
make format
.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context: Pybind11's 2.12 release is the first version to officially support Numpy 2.0. This PR updates Lightning's pybind11 version to ensure compatibility to/from numpy arrays.
Description of the Change: Updates Pybind11 version to the latest (2.13.5)
Benefits: Ensures direct compatibility with numpy 2.x
Possible Drawbacks: None.
Related GitHub Issues: