SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

 
 
Changelog for python311-BTrees-6.0-44.11.x86_64.rpm :

* Thu Jun 06 2024 Dirk Müller - update to 6.0:
* Drop support for Python 3.7.
* Build Windows wheels on GHA.
* Sat Apr 20 2024 Dirk Müller - update to 5.2:
* Add preliminary support for Python 3.13 as of 3.13a3.
* Thu Nov 02 2023 Matej Cepl - Update to 5.1:
* Drop using setup_requires due to constant problems on GHA.
* Add support for Python 3.12.
* Fri Jun 09 2023 ecsos - Add %{?sle15_python_module_pythons}
* Thu Feb 16 2023 Dirk Müller - update to 5.0:
* Build Linux binary wheels for Python 3.11.
* Drop support for Python 2.7, 3.5, 3.6.
* Mon Jan 02 2023 Dirk Müller - update to 4.11.3:
* point release to rebuild full set of wheels
* We no longer provide 32bit wheels for the Windows platform, only x86_64.
* Sun Nov 06 2022 Hans-Peter Jansen - version update to 4.11.0 (2022-11-03):
* Add support for Python 3.11.- version update to 4.10.1 (2022-09-12):
* Disable unsafe math optimizations in C code. (#184)- version update to 4.10.0 (2022-03-09):
* Add support for Python 3.10.- version update to 4.9.2 (2021-06-09):
* Fix fsBTree.TreeSet and fsBTree.BTree raising SystemError. See issue 170.
* Fix all the fsBTree objects to provide the correct interfaces and be instances of the appropriate collection ABCs. This was done for the other modules in release 4.8.0.
* Fix the multiunion, union, intersection, and difference functions when used with arbitrary iterables. Previously, the iterable had to be pre-sorted, meaning only sequences like list and tuple could reliably be used; this was not documented though. If the iterable wasn’t sorted, the function would produce garbage output. Now, if the function detects an arbitrary iterable, it automatically sorts a copy.- version update to 4.9.1 (2021-05-27):
* Fix setting unknown class attributes on subclasses of BTrees when using the C extension. This prevented subclasses from being decorated with AATTcomponent.adapter(). See issue 168.- version update to 4.9.0 (2021-05-26):
* Fix the C implementation to match the Python implementation and allow setting custom node sizes for an entire application directly by changing BTree.max_leaf_size and BTree.max_internal_size attributes, without having to create a new subclass. These attributes can now also be read from the classes in the C implementation. See issue 166.
* Add various small performance improvements for storing zope.interface attributes on BTree and TreeSet as well as deactivating persistent objects from this package.- disable more tests, that suffer from the same problem as testPurePython
* Thu Jan 13 2022 Matej Cepl - Add missing Provides
* Tue May 18 2021 pgajdosAATTsuse.com- version update to 4.8.0
* Make Python 2 forbid the use of type objects as keys (unless a custom metaclass is used that implements comparison as required by BTrees.) On Python 3, types are not orderable so they were already forbidden, but on Python 2 types can be ordered by memory address, which makes them unsuitable for use as keys. See `issue `_.
* Make the ``multiunion``, ``union``, ``intersection``, and ``difference`` functions accept arbitrary Python iterables (that iterate across the correct types). Previously, the Python implementation allowed this, but the C implementation only allowed objects (like ``TreeSet`` or ``Bucket``) defined in the same module providing the function. See `issue 24 `_.
* Fix persistency bug in the Python version (`#118 `_).
* Fix ``Tree.__setstate__`` to no longer accept children besides tree or bucket types to prevent crashes. See `PR 143 `_ for details.
* Make BTrees, TreeSet, Set and Buckets implements the ``__and__``, ``__or__`` and ``__sub__`` special methods as shortcuts for ``BTrees.Interfaces.IMerge.intersection``, ``BTrees.Interfaces.IMerge.union`` and ``BTrees.Interfaces.IMerge.difference``.
* Add support for Python 3.9.
* Build and upload aarch64 wheels.
* Make a value of ``0`` in the ``PURE_PYTHON`` environment variable require the C extensions (except on PyPy). Previously, and if this variable is unset, missing or unusable C extensions would be silently ignored. With this variable set to ``0``, an ``ImportError`` will be raised if the C extensions are unavailable. See `issue 156 `_.
* Make the BTree objects (``BTree``, ``TreeSet``, ``Set``, ``Bucket``) of each module actually provide the interfaces defined in ``BTrees.Interfaces``. Previously, they provided no interfaces.
* Make all the BTree and Bucket objects instances of ``collections.abc.MutableMapping`` (that is, ``isinstance(btree, MutableMapping)`` is now true; no actual inheritance has changed). As part of this, they now provide the ``popitem()`` method.
* Make all the TreeSet and Set objects instances of ``collections.abc.MutableSet`` (that is, ``isinstance(tree_set, MutableSet)`` is now true; no actual inheritance has changed). As part of this, they now provide several more methods, including ``isdisjoint``, ``discard``, and ``pop``, and support in-place mutation operators such as ``tree_set |= other``, ``tree_set += other``, ``tree_set -= other`` and ``tree_set ^= other``. See `issue 121 `_.
* Update the definitions of ``ISized`` and ``IReadSequence`` to simply be ``zope.interface.common.collections.ISized`` and ``zope.interface.common.sequence.IMinimalSequence`` respectively.
* Remove the ``__nonzero__`` interface method from ``ICollection``. No objects actually implemented such a method; instead, the boolean value is typically taken from ``__len__``.
* Adjust the definition of ``ISet`` to produce the same resolution order under the C3 and legacy orderings. This means that the legacy order has changed slightly, but that this package emits no warnings when ``ZOPE_INTERFACE_LOG_CHANGED_IRO=1``. Note that the legacy order was not being used for these objects because the C3 ordering was still consistent; it could only be obtained using ``ZOPE_INTERFACE_USE_LEGACY_IRO=1``. See `PR 159 `_ for all the interface updates.
* Fix the ``get``, ``setdefault`` and ``pop`` methods, as well as the ``in`` operator, to not suppress ``POSKeyError`` if the object or subobjects are corrupted. Previously, such errors were logged by ZODB, but not propagated. See `issue 161 `_.
* Tue Apr 14 2020 Tomáš Chvátal - Do not bother with documentation- Update to 4.7.2:
* Fix more cases of C and Python inconsistency.
 
ICM