Fix ambiguous str(handle) constructor for object-derived types
#5949
+29
−2
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.
Description
Fixes #5938
Templatize
str(handle h)with SFINAE to exclude types derived fromobject, resolving ambiguity withstr(const object&)when callingpy::str()on types likekwargs,dict, etc.The template now only accepts
handleorPyObject*, while allobject-derived types use thestr(const object&)overload.Piggy-backed: CIBW fixes (failing on master) commit 0e062f2
Suggested changelog entry:
str(handle)constructor when called withobject-derived types likekwargsordict. The constructor is now templatized with SFINAE to excludeobject-derived types, which use thestr(const object&)overload instead.