forked from pool/python-persistent
- Update to 4.3.0:
* Fix the possibility of a rare crash in the C extension when deallocating items. See https://github.com/zopefoundation/persistent/issues/66 * Change cPickleCache's comparison of object sizes to determine whether an object can go in the cache to use PyObject_TypeCheck(). This matches what the pure Python implementation does and is a stronger test that the object really is compatible with the cache. Previously, an object could potentially include cPersistent_HEAD and not set tp_base to cPersistenceCAPI->pertype and still be eligible for the pickle cache; that is no longer the case. See https://github.com/zopefoundation/persistent/issues/69 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-persistent?expand=0&rev=12
This commit is contained in:
@@ -1,3 +1,19 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Aug 14 14:55:56 UTC 2018 - mcepl@suse.com
|
||||
|
||||
- Update to 4.3.0:
|
||||
* Fix the possibility of a rare crash in the C extension when
|
||||
deallocating items. See
|
||||
https://github.com/zopefoundation/persistent/issues/66
|
||||
* Change cPickleCache's comparison of object sizes to determine
|
||||
whether an object can go in the cache to use PyObject_TypeCheck().
|
||||
This matches what the pure Python implementation does and is
|
||||
a stronger test that the object really is compatible with the
|
||||
cache. Previously, an object could potentially include
|
||||
cPersistent_HEAD and not set tp_base to cPersistenceCAPI->pertype
|
||||
and still be eligible for the pickle cache; that is no longer the
|
||||
case. See https://github.com/zopefoundation/persistent/issues/69
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Thu Jul 26 08:35:19 UTC 2018 - tchvatal@suse.com
|
||||
|
||||
|
Reference in New Issue
Block a user