-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix(regression): support embedded submodule #5650
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
Open
henryiii
wants to merge
9
commits into
pybind:master
Choose a base branch
from
henryiii:henryiii/fix/embeddedsubmod
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
e6f029c
tests: add test for embedded submodule
henryiii 69dc30a
tests: adjust
henryiii cd72edf
Update test_interpreter.cpp
henryiii edefef4
Update test_interpreter.cpp
henryiii c22a5b8
Update test_interpreter.cpp
henryiii a8bbfd3
Update test_interpreter.cpp
henryiii 96c7daa
Update pybind11.h
henryiii 1972a8a
fix: end instead of endif
henryiii e922cc5
Update include/pybind11/pybind11.h
henryiii File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh ... if we have to catch a
SystemError
here to accommodate submodules, I regret posting this comment on PR #5584.I think it'll be best to get rid of this
#else
branch then.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Python even throws exceptions when iterating over ranges. I would expect Python's low level C error handling to be more lightweight (if one can say that when it comes to python) than what happens if this were translated to a C++ exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be extremely rare, this is only for embedded submodules, normally it works. I think it's probably fine to leave this way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to you, I'm OK if you want to keep it.
What still makes me feel uneasy: the risk of masking unexpected
SystemError
s.Which is of course extremely low, but not zero. (Google experience: anything that can happen, does happen.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The function is part of the Stable API and just accesses a dictionary. My two cents: the current implementation is safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a link to the implementation handy?
What's on my mind: Why does it raise
SystemError
, and notAttributeError
?I'd feel more cozy ignoring an
AttributeError
.But as I said, I'm fine with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The function explicitly sets the system error. I could not see any system errors in the source of the dictionary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Seems like an unfortunate choice, to have it in the same class of exceptions as e.g. out-of-memory, but 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://docs.python.org/3/library/exceptions.html#SystemError
Doesn’t seem too bad, I think it’s for things like this, exceptions that shouldn’t make it up to the user.