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
Sometimes the above prints {'a': {'at1': 1, 'at2': 2}}
and sometimes
{'a': {'at1': 1, 'at2': 2, 'at3': 3}}
some analysis
This seems to be caused by get_handler() sometimes returning setitem and sometimes returning setattr. (Maybe the correct behavior in this case is to disallow ambiguous paths. But in any case it should return the same thing consistently).
This in turn is caused by different orderings in the assign op type tree (I think the type tree should be constant):
reproduce with
Sometimes the above prints
{'a': {'at1': 1, 'at2': 2}}
and sometimes
{'a': {'at1': 1, 'at2': 2, 'at3': 3}}
some analysis
This seems to be caused by get_handler() sometimes returning
setitem
and sometimes returningsetattr
. (Maybe the correct behavior in this case is to disallow ambiguous paths. But in any case it should return the same thing consistently).This in turn is caused by different orderings in the assign op type tree (I think the type tree should be constant):
for the first result, and
for the second.
The text was updated successfully, but these errors were encountered: