Hello community,
here is the log from the commit of package python-dogpile.cache for
openSUSE:Factory checked in at 2020-12-09 22:12:46
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-dogpile.cache (Old)
and /work/SRC/openSUSE:Factory/.python-dogpile.cache.new.2328 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-dogpile.cache"
Wed Dec 9 22:12:46 2020 rev:27 rq:853805 version:1.1.1
Changes:
--------
---
/work/SRC/openSUSE:Factory/python-dogpile.cache/python-dogpile.cache.changes
2020-10-26 16:19:11.823074296 +0100
+++
/work/SRC/openSUSE:Factory/.python-dogpile.cache.new.2328/python-dogpile.cache.changes
2020-12-09 22:12:47.735150624 +0100
@@ -1,0 +2,31 @@
+Wed Nov 25 14:10:35 UTC 2020 - Matej Cepl <[email protected]>
+
+- Update to 1.1.1:
+ - Fixed regression where the serialization and deserialization
+ functions could be inadvertently turned into instance methods with
+ an unexpected argument signature, namely when pickle.dumps and
+ pickle.loads are the pure Python version as is the case in pypy.
+ - Reworked the means by which values are serialized and deserialized
+ from backends, and provided for custom serialization of values.
+ Added the CacheRegion.serializer and CacheRegion.deserializer
+ parameters which may be set to any serializer.
+ - Serialization and deserialization now take place within the
+ CacheRegion so that backends may now assume string values in all
+ cases. This simplifies the existing backends and also makes custom
+ backends easier to write and maintain.
+ - Additionally, the serializer is now applied to the user-defined
+ value portion of the CachedValue and not to the metadata or other
+ portions of CachedValue object itself, so the serialized portion is
+ effectively a "payload" within the larger CachedValue structure that
+ is passed as part of the larger string format. The overall format is
+ a separate JSON of the cached value metadata, followed by the
+ serialized form. This allows for end-user serialization schemes that
+ are hardwired to the values themselves without the need to serialize
+ dogpile's internal structures as well.
+ - Existing custom backends should continue to work without issue; they
+ now have the option to forego any separate serialization steps, and
+ can also subclass a new backend BytesBackend that marks them as
+ a backend that only deals with bytes coming in and out; all internal
+ serialization logic from such a backend can be removed.
+
+-------------------------------------------------------------------
Old:
----
dogpile.cache-1.0.2.tar.gz
New:
----
dogpile.cache-1.1.1.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-dogpile.cache.spec ++++++
--- /var/tmp/diff_new_pack.nJeqN0/_old 2020-12-09 22:12:48.311151208 +0100
+++ /var/tmp/diff_new_pack.nJeqN0/_new 2020-12-09 22:12:48.315151212 +0100
@@ -19,14 +19,17 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
%global skip_python2 1
Name: python-dogpile.cache
-Version: 1.0.2
+Version: 1.1.1
Release: 0
+%define modname dogpile.cache
+%define modver 1_1_1
Summary: A caching front-end based on the Dogpile lock
License: BSD-3-Clause
Group: Development/Languages/Python
URL: https://github.com/sqlalchemy/dogpile.cache
-Source:
https://files.pythonhosted.org/packages/source/d/dogpile.cache/dogpile.cache-%{version}.tar.gz
+Source:
https://github.com/sqlalchemy/%{modname}/archive/rel_%{modver}.tar.gz#/%{modname}-%{version}.tar.gz
BuildRequires: %{python_module Mako}
+BuildRequires: %{python_module dbm}
BuildRequires: %{python_module decorator >= 4.0.0}
BuildRequires: %{python_module mock}
BuildRequires: %{python_module pytest}
@@ -48,7 +51,7 @@
new value.
%prep
-%setup -q -n dogpile.cache-%{version}
+%setup -q -n %{modname}-rel_%{modver}
%build
%python_build
++++++ dogpile.cache-1.0.2.tar.gz -> dogpile.cache-1.1.1.tar.gz ++++++
++++ 27856 lines of diff (skipped)
_______________________________________________
openSUSE Commits mailing list -- [email protected]
To unsubscribe, email [email protected]
List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
List Archives:
https://lists.opensuse.org/archives/list/[email protected]
