Merged
Conversation
tmontaigu
force-pushed
the
pybind11-3.0
branch
5 times, most recently
from
51f0089 to
a0b5b7e
Compare
First step of the upgrade process. The smart_holder capabilities are probably going to interest us. Some py::enum_ where empty, this made 'finalization' of pybind11's internals fail, so we had to populate these enums.
tmontaigu
force-pushed
the
pybind11-3.0
branch
from
a0b5b7e to
52dfd67
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
First step of the upgrade process.
The smart_holder capabilities are probably going to interest us.
Some py::enum_ where empty, this made 'finalization' of pybind11's internals
fail, som we had to populate these enums.