Mark Dickinson

Maybe sort by weight and class depth (in the sense of the shortest path from the class to `object` in the 'is_a_direct_subclass' DAG)?

See #883 for one approach to solving this; I've closed that PR, but we may want to pick up the code from that PR again as a basis for a...

But for something like `Int("ABC")` (rather than using a dynamic default), I don't think there's anything stopping us from raising at `TraitType` instantiation time.

For example, `Range` already does this: ``` >>> from traits.api import HasTraits, Range >>> class A(HasTraits): ... foo = Range(2, 3j) ... Traceback (most recent call last): File "", line...

Adding to the 6.1.0 milestone for the specific case of making sure that things work for `PrefixMap`.

Another example of the general case: ```python >>> from traits.api import * >>> class A(HasTraits): ... foo = Int(True) ... >>> a = A() >>> a.foo True # surprise! expect...

Not for this release.

> I also wish there is an alternative to doing these things in `setUp` and `tearDown` for it is often cumbersome when dealing with multiple test base classes How about...

It's possible that the intent here is that if either of `low` or `high` is dynamic, then both should be.

Okay, thanks. Reclassified.