forked from pool/python-wrapt
- update to 1.15.0:
* When the C extension for wrapt was being used, and a property
was used on an object proxy wrapping another object to intercept
access to an attribute of the same name on the wrapped object,
if the function implementing the property
raised an exception, then the exception was ignored and not
propagated back to the caller.
* Address issue where the post import hook mechanism of wrapt
wasn't transparent and left the __loader__ and __spec__.loader
attributes of a module as the wrapt import hook loader and
not the original loader.
* Address issues where a thread deadlock could occur within the
wrapt module import handler, when code executed from a post
import hook created a new thread and code executed in the
context of the new thread itself tried to register a post
import hook, or imported a new module.
* When using ``CallableObjectProxy`` as a wrapper for a type or
function and calling the wrapped object, it was not possible
to pass a keyword argument named ``self``.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-wrapt?expand=0&rev=33
This commit is contained in:
@@ -1,3 +0,0 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:866211ed43c2639a2452cd017bd38589e83687b1d843817c96b99d2d9d32e8d7
|
||||
size 133767
|
||||
BIN
1.15.0.tar.gz
(Stored with Git LFS)
Normal file
BIN
1.15.0.tar.gz
(Stored with Git LFS)
Normal file
Binary file not shown.
@@ -1,3 +1,26 @@
|
||||
-------------------------------------------------------------------
|
||||
Thu May 4 20:43:27 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
- update to 1.15.0:
|
||||
* When the C extension for wrapt was being used, and a property
|
||||
was used on an object proxy wrapping another object to intercept
|
||||
access to an attribute of the same name on the wrapped object,
|
||||
if the function implementing the property
|
||||
raised an exception, then the exception was ignored and not
|
||||
propagated back to the caller.
|
||||
* Address issue where the post import hook mechanism of wrapt
|
||||
wasn't transparent and left the __loader__ and __spec__.loader
|
||||
attributes of a module as the wrapt import hook loader and
|
||||
not the original loader.
|
||||
* Address issues where a thread deadlock could occur within the
|
||||
wrapt module import handler, when code executed from a post
|
||||
import hook created a new thread and code executed in the
|
||||
context of the new thread itself tried to register a post
|
||||
import hook, or imported a new module.
|
||||
* When using ``CallableObjectProxy`` as a wrapper for a type or
|
||||
function and calling the wrapped object, it was not possible
|
||||
to pass a keyword argument named ``self``.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Fri Apr 21 12:38:55 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
|
||||
%{?sle15_python_module_pythons}
|
||||
Name: python-wrapt
|
||||
Version: 1.14.1
|
||||
Version: 1.15.0
|
||||
Release: 0
|
||||
Summary: A Python module for decorators, wrappers and monkey patching
|
||||
License: BSD-2-Clause
|
||||
|
||||
Reference in New Issue
Block a user