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
Now that we're Python 3 only, we don't need TraitSetObject.copy any more. It's harmless, except in that it misleads people (me) into expecting that TraitDictObject.copy and TraitListObject.copy should exist, too.
OTOH, we should also make sure that there are tests for calling the .copy method on the value of a Set trait.
Now that we're Python 3 only, we don't need
TraitSetObject.copy
any more. It's harmless, except in that it misleads people (me) into expecting thatTraitDictObject.copy
andTraitListObject.copy
should exist, too.OTOH, we should also make sure that there are tests for calling the
.copy
method on the value of aSet
trait.See #97, #98.
The text was updated successfully, but these errors were encountered: