Skip to content
This repository has been archived by the owner on Dec 10, 2024. It is now read-only.

Build: Switch from pybind to nanobind #110

Merged
merged 5 commits into from
Oct 29, 2024

Conversation

iopapamanoglou
Copy link
Contributor

Build: Switch from pybind to nanobind

Description

nanobind is faster in compiling and executing because it's lighter
Has better support for pyi stub generation.

Fixes # (issue)

Checklist

Please read and execute the following:

  • My code follows the coding guidelines of this project
  • My PR title is following the contribution guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (if applicable)
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I ran Black to format my code

Code of Conduct

By submitting this issue, you agree to follow our Code of Conduct:

nanobind is faster in compiling and executing because it's lighter
Has better support for pyi stub generation.
@iopapamanoglou iopapamanoglou merged commit 2f9eba9 into main Oct 29, 2024
6 checks passed
@iopapamanoglou iopapamanoglou deleted the feature/switch_to_nanobind branch October 29, 2024 14:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant