python-traits
The traits package developed by Enthought provides a special type
definition called a trait. Although they can be used as normal Python object
attributes, traits also have several additional characteristics:
* Initialization: A trait can be assigned a default value.
* Validation: A trait attribute's type can be explicitly declared.
* Delegation: The value of a trait attribute can be contained either
in another object.
* Notification: Setting the value of a trait attribute can trigger
notification of other parts of the program.
* Visualization: User interfaces that permit the interactive
modification of a trait's value can be automatically constructed
using the trait's definition.
- Developed at devel:languages:python:numeric
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/python-traits && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_multibuild | 0000000053 53 Bytes | |
fix-test.patch | 0000000640 640 Bytes | |
python-traits.changes | 0000021441 20.9 KB | |
python-traits.spec | 0000003808 3.72 KB | |
traits-6.4.3.tar.gz | 0005067947 4.83 MB |
Latest Revision
Ana Guerrero (anag+factory)
accepted
request 1138237
from
Dirk Mueller (dirkmueller)
(revision 10)
- update to 6.4.3: * This is a bugfix release that fixes test failures with Sphinx 7.2 and later, and adds support for Python 3.12 * Rename requires_numpy_testing decorator to requires_numpy_typing, and have it check for numpy.typing, not numpy.testing. * Fix missing numpy_examples directory in traits-stubs package data. * Validation of items within a container (e.g., foos = List(MyTraitType)) now always matches the validation used for the item trait at top level (e.g., foo = MyTraitType). Previously, the validation methods used could differ, thanks to a bug in the container implementations. For most trait types this will make no difference, but for the Tuple trait type this change has the consequence that lists will no longer be accepted as valid for Tuple traits inside list items. See issue #1619 and PR #1625 for more information. * Related to the above: a top-level Tuple() trait declaration currently accepts Python list objects, while a Tuple declaration with explicit item types (for example Tuple(Int(), Int())) does not. The support for list objects in plain Tuple() is deprecated, and will be removed in a future version of Traits. See PR #1627 for more information. * The following people contributed code changes for this release: * Caio Agiani * Steve Allen * Mark Dickinson * Sai Rahul Poruri * Corran Webster Features ~~~~~~~~ * ETSConfig attributes now support deletion. This makes it easier to make * Complex trait type validation is now more lenient: any type that implements __complex__ will be accepted.
Comments 0