Accepting request 507327 from home:alois:branches:devel:languages:python

OBS-URL: https://build.opensuse.org/request/show/507327
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-transaction?expand=0&rev=31

python-transaction.changes

@@ -1,3 +1,82 @@
+-------------------------------------------------------------------
+Sat Jun 24 11:52:07 UTC 2017 - aloisio@gmx.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 09:56:45 UTC 2015 - benoit.monin@gmx.fr