Tri.declarative

Latest version: v5.7.0

Safety actively analyzes 630169 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

4.0.0

------------------

* `get_meta()` now collects extra arguments in a `Namespace` to get consistent override behaviour.

* `should_show` no longer accepts a callable as a valid return value. It will assert on this, because it's always a mistake.

* Added `evaluate_strict` and `evaluate_recursive_strict` that will not accept callables left over after the evaluation. If possible prefer these methods because they will stop the user of your library from making the mistake of not matching the given signature and ending up with an unevaluated callable in the output.

3.1.0

------------------

* Fixed issues when Namespace contained a key called any of items, values, keys, or get

* Removed sorting on Namespace kwargs that isn't needed in python 3 anymore. The sorting also destroys the given order which can be surprising

* Removed old obsolete functions collect_namespaces, extract_subkeys, and setdefaults

3.0.0

------------------

* Renamed module from `tri.declarative` to `tri_declarative`. This is a breaking change

* Dropped support for python2

2.0.0

------------------

* Fixed `get_signature` cache to not pollute struct-like dicts

* New call_target semantics for class method shortcuts, this is a potential breaking change

1.2.1

------------------

* Improved documentation output

1.2.0

------------------

* Add get_members function to enable reuse of declarative attribute collection

* Add class_shortcut decorator to enable with_meta aware class shortcuts

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.