Fix ConfigDict
's handling of unicode keys
#13
Merged
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.
Make
ConfigDict.__setitem__
call_autocast
before checking the key type, just likeDict
does. Add a unicode key in the unit test for each so that this is tested (and I confirmed the fix by commenting out the call to_autocast
in both dict classes, and two tests failed.This solves a problem that pybind11 returns unicode strings from C++ methods that return std::string; the problem was showing up in afw's
testCameraGeom.py
.