Transaction

Latest version: v5.0

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

Scan your dependencies

Page 2 of 6

2.4.0

==================

- Changed the implementation of ThreadTransactionManager to be a
thread.local that wraps a TransactionManager rather than a
thread.local that inherits from TransactionManager. It now exposes a
manager attribute that allows access to the wrapped transaction
manager to allow cross thread calls. See `issue 68
<https://github.com/zopefoundation/transaction/pull/68>`_.

2.3.0

==================

- Add support for Python 3.7.

- Reach 100% test coverage.

- Fix ``transaction.manager.run`` formatting transaction notes when
given a mix of byte and text strings, such as can happen in Python 2
with ``unicode_literals``.

2.2.1

==================

- Make documentation index more user friendly; move old docs to developer
section.

- Don't crash when printing tracebacks in IPython on Python 2.
(This addresses https://github.com/zopefoundation/transaction/issues/5.)

2.2.0

==================

- Add support for Python 3.6.

- Drop support for Python 3.3.

- Add ``isRetryableError`` to the
``transaction.interfaces.ITransaction`` interface to allow external
systems to query whether an exception is retryable (transient) by
any of the attached data managers. Any
``transaction.interfaces.TransientError`` is considered retryable
but a data manager may also consider other exceptions on a
per-instance basis.

See https://github.com/zopefoundation/transaction/pull/38

2.1.2

==================

- To avoid leaking memory, don't include unexpected value in warnings
about non-text transaction meta data.

2.1.1

==================

- For backward compatibility, relax the requirements that transaction
meta data (user or description) be text:

- If None is assigned, the assignment is ignored.

- If a non-text value is assigned, a warning is issued and the value
is converted to text. If the value is a binary string, it will be
decoded with the UTF-8 encoding the ``replace`` error policy.

Page 2 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.