Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

python311-BTrees-devel-5.1-1.3 RPM for riscv64

From OpenSuSE Ports Tumbleweed for riscv64

Name: python311-BTrees-devel Distribution: openSUSE Tumbleweed
Version: 5.1 Vendor: openSUSE
Release: 1.3 Build date: Fri Nov 3 00:38:51 2023
Group: Unspecified Build host: reproducible
Size: 12642 Source RPM: python-BTrees-5.1-1.3.src.rpm
Packager: https://bugs.opensuse.org
Url: https://github.com/zopefoundation/BTrees
Summary: Development files for the python-BTrees module
This package contains the files needed for binding the python311-BTrees C module.

Provides

Requires

License

ZPL-2.1

Changelog

* Thu Nov 02 2023 Matej Cepl <mcepl@cepl.eu>
  - 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 <ecsos@opensuse.org>
  - Add %{?sle15_python_module_pythons}
* Thu Feb 16 2023 Dirk Müller <dmueller@suse.com>
  - 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 <dmueller@suse.com>
  - 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 <hpj@urpla.net>
  - 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 @component.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 <mcepl@suse.com>
  - Add missing Provides
* Tue May 18 2021 pgajdos@suse.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
      <https://github.com/zopefoundation/BTrees/issues/153>`_.
    * 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
      <https://github.com/zopefoundation/BTrees/issues/24>`_.
    * Fix persistency bug in the Python version
      (`#118 <https://github.com/zopefoundation/BTrees/issues/118>`_).
    * Fix ``Tree.__setstate__`` to no longer accept children besides
      tree or bucket types to prevent crashes. See `PR 143
      <https://github.com/zopefoundation/BTrees/pull/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
      <https://github.com/zopefoundation/BTrees/issues/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 <https://github.com/zopefoundation/BTrees/issues/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
      <https://github.com/zopefoundation/BTrees/pull/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
      <https://github.com/zopefoundation/BTrees/issues/161>`_.
* Tue Apr 14 2020 Tomáš Chvátal <tchvatal@suse.com>
  - Do not bother with documentation
  - Update to 4.7.2:
    * Fix more cases of C and Python inconsistency.
* Wed Mar 25 2020 Marketa Calabkova <mcalabkova@suse.com>
  - update to 4.7.1
    * Ensure the interface resolution order of all objects is consistent.
      See `issue 137 <https://github.com/zopefoundation/BTrees/issues/137>`_.
    * Add unsigned variants of the trees. These use the initial "U" for
      32-bit data and "Q" for 64-bit data (for "quad", which is similar to
      what the C ``printf`` function uses and the Python struct module
      uses).
    * Fix the value for ``BTrees.OIBTree.using64bits`` when using the pure Python
      implementation (PyPy and when ``PURE_PYTHON`` is in the environment).
    * Make the errors that are raised when values are out of range more
      consistent between Python 2 and Python 3 and between 32-bit and
      64-bit variants.
    * Make the Bucket types consistent with the BTree types as updated in
      versions 4.3.2: Querying for keys with default comparisons or that
      are not integers no longer raises ``TypeError``.
* Mon Jan 13 2020 Marketa Calabkova <mcalabkova@suse.com>
  - update to 4.6.1
    * Add support for Python 3.8.

Files

/usr/lib64/python3.11/site-packages/BTrees/SetOpTemplate.h
/usr/lib64/python3.11/site-packages/BTrees/_compat.h
/usr/lib64/python3.11/site-packages/BTrees/floatvaluemacros.h
/usr/lib64/python3.11/site-packages/BTrees/intkeymacros.h
/usr/lib64/python3.11/site-packages/BTrees/intvaluemacros.h
/usr/lib64/python3.11/site-packages/BTrees/objectkeymacros.h
/usr/lib64/python3.11/site-packages/BTrees/objectvaluemacros.h


Generated by rpm2html 1.8.1

Fabrice Bellet, Sun Apr 21 23:21:28 2024