-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Wrong error triggered in calls with keyword arguments #688
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
Comments
It is actually worse than I thought. Not only is the error confusing. It actually shouldn't error at all when the missing argument has a default value. But it does... |
(Is this happening with 2.0.1?) |
It works on 2.0.1. |
I.e. is broken on master but not on 2.0.1. |
jagerman
added a commit
to jagerman/pybind11
that referenced
this issue
Feb 24, 2017
Fixes pybind#688. My (commented) assumption that such an error is "highly likely to be a caller mistake" was proven false by pybind#688.
I should have known that something I assumed to be "highly likely" would fail before long (see the diff). Fixed in #696. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a class with an overloaded copy constructor:
wrapped as
Is called with:
The error message reads:
TypeError: __init__(): got multiple values for argument 'deep'
. Which is confusing.The text was updated successfully, but these errors were encountered: