Mark Dickinson

@aaronayres35 Yes, I think so. I've changed the milestone for this issue.

Re-opening: #1421 improved the situation, but there's still work to do.

I'm also seeing non-fixed-width fonts in code samples; see the #1421 discussion for details.

Hmm. The `on_trait_change` behaviour is less clear cut than I thought: For example, after: ```python from traits.api import HasTraits, Int, Str def print_event(obj, name, old, new): print(obj, name, old, new)...

Not for this release.

Sounds good to me. Putting in the 6.2.0 milestone (but I won't complain if we find time to do it for 6.1.0).

Bumping.

Here's an example of the problematic behaviour: our dynamic Enum value is modified at get time for a single instance, but not for an Enum inside a List: ```python from...

In _theory_, we could rework the getters for Lists, Tuples, etc. to invoke the getters for individual traits. In practice, that's going to be a lot of work, and it's...

> One way in which this is problematic (there are others) To elaborate on this: the main problem with this get-time value changing is that the apparent value of the...