Changelog for python310-transaction-3.0.1-1.1.noarch.rpm :

* Wed Apr 20 2022 pgajdosAATTsuse.com- do not require python-mock for build
* Wed Jan 13 2021 pgajdosAATTsuse.com- version update to 3.0.1 - Exception raised by a before commit hook is no longer hidden. No further commit hooks are called and exception is propagated to the caller of ``commit()``. See `#95 `_.- use %pytest macro
* Mon May 04 2020 Tomáš Chvátal - Do not be quiet on test run
* Wed Mar 11 2020 pgajdosAATTsuse.com- version update to 3.0.0 - Drop support for Python 3.4. - Add support for Python 3.8. - Drop support for legacy transaction APIs including ``Transaction.register()`` and old ZODB3-style datamanagers. See `issue 89 `_. - ``TransactionManager.run`` now commits/aborts the transaction \"active\" after the execution of
*func
* (and no longer the initial transaction which might already have been committed/aborted by
*func
*) (`#58 `_). It aborts the transaction now for all exceptions raised by
*func
* - even if it is only an instance of `BaseException` but not of `Exception`, such as e.g. a ``SystemExit`` or ``KeyboardInterupt`` exception. - Support abort hooks (symmetrically to commit hooks) (`#77 `_). - Make Transaction drop references to its hooks, manager, synchronizers and data after a successful ``commit()`` and after
* any
* ``abort()``. This helps avoid potential cyclic references. See `issue 82 `_. - Allow synchronizers to access ``Transaction.data()`` when their ``afterCompletion`` method is called while aborting a transaction. - Make it safe to call ``Transaction.abort()`` more than once. The second and subsequent calls are no-ops. Previously a ``ValueError(Foreign transaction)`` would be raised.
* Mon Oct 14 2019 Matej Cepl - Replace %fdupes -s with plain %fdupes; hardlinks are better.
* Mon Mar 04 2019 Tomáš Chvátal - Update to 2.4.0:
* add support for python 3.7
* many small fixes and test improvements
* For more see CHANGES.rst
* Sat Jun 24 2017 aloisioAATTgmx.com- Update to version 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. 2.1.0:
* Added a transaction-manager explicit mode. Explicit mode makes some kinds of application bugs easier to detect and potentially allows data managers to manage resources more efficiently. (This addresses https://github.com/zopefoundation/transaction/issues/35.) 2.0.3:
* The user and description fields must now be set with text (unicode) data. Previously, if bytes were provided, they’d be decoded as ASCII. It was decided that this would lead to bugs that were hard to test for.
* Also, the transaction meta-data field, extended_info has been renamed to extension. 2.0.2:
* Fixed: Some legacy applications expect the transaction _extension attribute to be mutable and it wasn’t. 2.0.1:
* The transaction user and description attributes are now defined to be text (unicode) as opposed to Python the str type.
* Added the extended_info transaction attribute which contains transaction meta data. (The _extension attribute is retained as an alias for backward compatibility.)
* The transaction interface, ITransaction, now requires extended_info keys to be text (unicode) and values to be JSON-serializable.
* Removed setUser from ITransaction. We’ll keep the method indefinitely, but it’s unseemly in ITransaction. :) The main purpose of these changes is to tighten up the text specification of user, description and extended_info keys, and to give us more flexibility in the future for serializing extended info. It’s possible that these changes will be breaking, so we’re also increasing the major version number. 1.7.0:
* Added a transaction-manager run method for running a function as a transaction, retrying as necessary on transient errors.
* Fixed the transaction manager attempts method. It didn’t stop repeating when there wasn’t an error.
* Corrected ITransaction by removing beforeCommitHook (which is no longer implemented) and removing ‘self’ from two methods. 1.6.1:
* Fixed: Synchonizers that registered with transaction managers when transactions were in progress didn’t have their newTransaction methods called to let them know of the in-progress transactions. 1.6.0:
* New transaction API for storing data on behalf of objects, such as data managers.
* Drop references to data managers joined to a transaction when it is committed or aborted. 1.5.0:
* Drop support for Python 2.6 and 3.2.
* Add support for Python 3.5.
* Added APIs for interogating and clearing internal state to support client tests. 1.4.4:
* Use the standard valuerefs() method rather than relying on implementation details of WeakValueDictionary in WeakSet.
* Add support for PyPy3.
* Require 100% branch coverage (in addition to 100% statement coverage).- Converted to single-spec
* Thu May 14 2015 benoit.moninAATTgmx.fr- update to version 1.4.3:
* Added support for Python 3.4.
* release 1.4.2 (skipped)- switch the source archive to tar.gz- pass -q to the test to avoid spamming the build log
* Fri Aug 02 2013 hpjAATTurpla.net- Update to 1.4.1 version:
* Document that values returned by sortKey must be strings, in order to guarantee total ordering.
* Fix occasional RuntimeError: dictionary changed size during iteration errors in transaction.weakset on Python 3.- Generate and install documentation in separate package- Run tests
* Tue Jan 15 2013 p.drouandAATTgmail.com- Initial python3 support