Corran Webster

The immediate issue is resolved by pinning in #1169 I am going to close this in favour of #1164, with a reference back to the discussion here.

Thanks for noticing - we missed updating these on the last release. Pyface (and TraitsUI) _should_ work on 3.9 and 3.10 (and presumably 3.11 when it comes out), supports Qt5...

Thanks for the contribution and apologies for the delay in responding! I might need to do a manual check to see if this causes a problem with PyQt6 in addition...

I think that the current `main` branch needs to be merged in to this PR branch before tests will pass.

Have you tested under PyQt - I haven't because I don't currently have PyQt installed on my machine. If this is a PySide issue, I agree that it's not Enaml's...

I don't remember entirely, but looking again right now, there are things like that `appdirs` version of the "user data directory" is different from ETSConfig's (appdirs is "where you put...

My suspicion is that maybe https://github.com/enthought/traits/blob/ba7c10fa28666219e276c7eeeac7e3e7168a45c2/traits/has_traits.py#L633 should be setting into the base trait dict as well as the class trait dict? Either that or `class_traits` should be using `__class_traits__` as...

Worth noting for the discussion that this is not adding new functionality, just exposing something already implemented in the API. The current work-around is to do: ``` @observe(trait("foo").trait("updated", optional=True)) def...

Adding a note here if we ever do this: care would be needed to handle what to do when cloning such a trait with a new default value, as well...

A note that https://github.com/enthought/enable/issues/945 is a different twist on the same root problem.