traits
traits copied to clipboard
enthought
Observable typed attributes for Python classes
Following [PEP 604](https://www.python.org/dev/peps/pep-0604/) which allows constructs like `int | float` as a replacement for `Union[int, float]` should we allow `Int | Float` as an (optional) replacement for `Union(Int, Float)`? The...
Or perhaps even better, deprecate all the directory management and tell people to use `appdirs` instead? Default user directories could then be an application configuration option. We would need some...
The CSS used for styling the appearance of the Traits tutorial in the `etsdemo` app could use some work. See discussion in #1418 and #1419.
In the following example, an `AttributeError` is raised complaining that the `foo` attribute is `None` even though the `foo` attribute is supplied at instantiation. My fuzzy understanding is that the...
When an attribute has a `Date` type, then it is meant to be just *Date*, not *Date and Time*. So I would expect assigning a `datetime` object to a Date...
It might be useful to have a short section of documentation describing what ETSConfig is / what it is useful for and how to use it. There is some mention...
Ref: https://github.com/enthought/pyface/pull/866 With traits 6.2 we are explicitly stating in documentation that imports should come from api modules. Because of this I decided to run through pyface for any non...
It is common to have `Union` traits of the form `Union(None, )`. As a convenience to developers, and following a similar convention in Python's `typing` module, we should consider having...
It would be good to review and rework the main landing page for the Traits documentation. In particular, it would be desirable to have a brief introduction to Traits on...
Current Traits allows an `Instance` trait to be given an instance rather than a type as the first argument. It then replaces that instance with its type. So for example,...