Node

Latest version: v1.2.1

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

Scan your dependencies

Page 2 of 6

0.9.27

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

- Expose ``first_key``, ``last_key``, ``next_key`` and ``prev_key`` from
odict storage on ``Order`` behavior.
[rnix, 2021-10-21]

- Add basic serializer settings mechanism.
[rnix, 2021-07-20]

0.9.26

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

- Use ``node.utils.safe_decode`` in ``node.behaviors.nodify.Nodify.treerepr``.
[rnix, 2021-05-04]

- Add ``node.utils.safe_encode`` and ``node.utils.safe_decode``.
[rnix, 2021-05-04]

0.9.25

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

- Introduce ``uuid_factory`` function on ``node.interfaces.IUUIDAware`` and
implement default function in ``node.behaviors.common.UUIDAware``.
[rnix, 2020-03-01]

- Rename ``NodeTestCase.expect_error`` to ``NodeTestCase.expectError``.
[rnix, 2019-09-04]

- Rename ``NodeTestCase.check_output`` to ``NodeTestCase.checkOutput``.
[rnix, 2019-09-04]

- Introduce ``prefix`` keyword argument in ``Nodify.treerepr``.
[rnix, 2019-09-04]

0.9.24

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

- Overhaul ``node.behaviors.Order``. Use related functions from ``odict`` where
appropriate.
[rnix, 2019-07-10]

- Remove superfluous ``extra_require`` from ``setup.py``.
[rnix, 2019-04-25]

- Drop Support for python < 2.7 and < 3.3.
[rnix, 2019-04-25]

0.9.23

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

- Use property decorators for ``node.behaviors.reference.Reference.uuid``.
[rnix, 2017-12-15]

0.9.22

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

- Add ``always_dispatch`` keyword argument to
``node.behaviors.events.EventAttribute`` constructor which defines whether
events are always dispatched on ``__set__``, not only if attribute value
changes.
[rnix, 2017-06-20]

- Use ``node.utils.UNSET`` as default ``default`` value in
``node.behaviors.events.EventAttribute.__init__``.
[rnix, 2017-06-19]

- Introduce ``node.behaviors.events.EventAttribute.subscriber`` decorator which
can be used to register attribute subscribers.
[rnix, 2017-06-19]

- Move event dispatching related classes and functions from ``node.events``
to ``node.behaviors.events`` and import it from there in ``node.events``.
[rnix, 2017-06-16]

- Introduce ``node.interfaces.IEvents`` and implement
``node.behaviors.events.Events`` behavior. Contains business logic from
``node.events.EventDispatcher``. Use new behavior on ``EventDispatcher``.
[rnix, 2017-06-16]

- Create ``suppress_events`` context manager which can be used to
suppress event notification in conjunction with ``node.behaviors.Events``
behavior.
[rnix, 2017-06-15]

- Create ``node.behaviors.fallback.fallback_processing`` context manager and
and use it in ``node.behaviors.fallback.Fallback.__getitem__`` to check
whether fallback processing is active.
[rnix, 2017-06-15]

Page 2 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.