-
Notifications
You must be signed in to change notification settings - Fork 373
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle older numpy versions / py 3.8 in
VecND
extensions (#2896)
What the title says. This is what prevented us from doing the logical thing in `Arrow3D` extensions (and became even more of an issue after I made the `PointND` components use `VecND` internally in #2894). ### What ### Checklist * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested [demo.rerun.io](https://demo.rerun.io/pr/2896) (if applicable) - [PR Build Summary](https://build.rerun.io/pr/2896) - [Docs preview](https://rerun.io/preview/pr%3Acmc%2Ffix_vecnd_vs_numpy/docs) - [Examples preview](https://rerun.io/preview/pr%3Acmc%2Ffix_vecnd_vs_numpy/examples)
- Loading branch information
Showing
3 changed files
with
36 additions
and
6 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters