python: switch binding library to nanobind
#948
Conversation
This file contains hidden or 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
|
Sorry for not reacting to your PR so far. This is definitively interesting, I just don't have the time right now to properly look into this. But I will at some point in time. |
|
No worries, take your time! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates the Python bindings for
zxingcppfrompybind11tonanobind.Key Benefits:
Enhanced IDE Support (Autocompletion & Type Hinting):
The primary driver for this change is
nanobind's straightforward support for generating stub files (.pyi). These stubs enable autocompletion and type hinting in IDEs, significantly improving the development experience when using thezxingcpplibrary.Smaller Binary Sizes
Faster Compilation Times
Important Structural Change:
nanobind's typical project structure, thezxingcppPython extension has been refactored from a single-file module (e.g.,zxingcpp.pydorzxingcpp.so) into a Python package (a directory namedzxingcppcontaining an__init__.pyand the compiled extension module).