Skip to content

Make bad kwarg arguments try next overload #696

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

Merged
merged 3 commits into from
Feb 24, 2017

Conversation

jagerman
Copy link
Member

Fixes #688.

My (commented) assumption that such an error is "highly likely to be a caller mistake" was proven false by #688.

Fixes pybind#688.

My (commented) assumption that such an error is "highly likely to be a
caller mistake" was proven false by pybind#688.
With the previous commit, output can be very confusing because you only
see positional arguments in the "invoked with" line, but you can have a
failure from kwargs as well (in particular, when a value is invalidly
specified via both via positional and kwargs).  This commits adds
kwargs to the output, and updates the associated tests to match.
@wjakob
Copy link
Member

wjakob commented Feb 24, 2017

Merged, thank you!

@wjakob wjakob merged commit 2c98e45 into pybind:master Feb 24, 2017
@jagerman
Copy link
Member Author

Arg, that workaround still triggers a style failure: it needs spaces around the +

@jagerman
Copy link
Member Author

You could also just revert the fix entirely and instead just don't apply that check for .py files (it really is mainly aimed at C++ style anyway).

@wjakob
Copy link
Member

wjakob commented Feb 24, 2017

I amended that commit

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

Successfully merging this pull request may close these issues.

2 participants