You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to the latest version of dpath (from 2.0.6 to 2.1.2) I noticed that dpath.util.merge was no longer working as expected since it started returning a tuple instead of the expected dictionary.
After some debugging, I found that this function is now deprecated (moved to the top level). However, the deprecated function seems to contain a bug in the form of a trailing comma. The trailing comma causes the result to be a tuple, instead of a dictionary.
Example: db.util.merge({"key1": 1}, {"key2": 2}) -> ({"key1": 1, "key2": 2},) instead of the expected db.utilmerge({}, {}) -> {"key1": 1, "key2": 2}
The text was updated successfully, but these errors were encountered:
After upgrading to the latest version of
dpath
(from 2.0.6 to 2.1.2) I noticed thatdpath.util.merge
was no longer working as expected since it started returning a tuple instead of the expected dictionary.After some debugging, I found that this function is now deprecated (moved to the top level). However, the deprecated function seems to contain a bug in the form of a trailing comma. The trailing comma causes the result to be a tuple, instead of a dictionary.
Example:
db.util.merge({"key1": 1}, {"key2": 2}) -> ({"key1": 1, "key2": 2},)
instead of the expecteddb.utilmerge({}, {}) -> {"key1": 1, "key2": 2}
The text was updated successfully, but these errors were encountered: