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

Investigate switching from pybind11 to nanobind #1800

Open
cqc-alec opened this issue Mar 4, 2025 · 2 comments
Open

Investigate switching from pybind11 to nanobind #1800

cqc-alec opened this issue Mar 4, 2025 · 2 comments
Assignees

Comments

@cqc-alec
Copy link
Collaborator

cqc-alec commented Mar 4, 2025

It seems nanobind is a more modern alternative to pybind11 (from the same original developer), with similar syntax but better performance and support for stable ABI (for Python 3.12+).

@cqc-alec cqc-alec self-assigned this Mar 4, 2025
@CalMacCQ
Copy link
Contributor

CalMacCQ commented Mar 4, 2025

Would this have any implications for the cpp files which are used as source material for the sphinx docs? Sphinx doesn't always play nicely with some of the syntax in these files.

@cqc-alec
Copy link
Collaborator Author

cqc-alec commented Mar 4, 2025

Would this have any implications for the cpp files which are used as source material for the sphinx docs? Sphinx doesn't always play nicely with some of the syntax in these files.

It would certainly have implications for the binder source files. I don't think sphinx directly processes these. Can you give an example?

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

No branches or pull requests

2 participants