python3-BTrees-devel-4.7.2-bp155.2.10 >  A dkWII%z 'c<[HWCfx<1 }(^W3:1# >i HjN C 6 2(^ƵΔ9JZ}@іlSpO_cBx&ܳi<)0]<ά~qy "[Wa-;pqv<~9Z¨)lKzDžAhdU ]tԪY#̞s/RSΛzߛ|G5Z(ϲӦ.?e03txy:g E,QyDsg/Ea|>l9V$4PlJ%)TC<5f$ ad Ո@+Yi^Zlh):Iϝ^&N(p[a'#VW3.-bad M1a i!Y"@S 1CеJdpRy LDI v_zA0ӸȒjwIZ]pGиCΰ_5!#+.g &g}`A%9 @ڕ^LVm>#?5׽W{mլxa?hvO/g&p;"?"d ( W  5;D\ h t   0Nlf(8 9 : FG H I 4X <Y D\ h] ^ b!c!d"&e"+f".l"0u"Dv"\z"|""""Cpython3-BTrees-devel4.7.2bp155.2.10Development files for the python-BTrees moduleThis package contains the files needed for binding the python3-BTrees C module.dkW9lamb532QSUSE Linux Enterprise 15 SP5openSUSEZPL-2.1https://bugs.opensuse.orgUnspecifiedhttps://github.com/zopefoundation/BTreeslinuxx86_647́^p^p^p^p^p^p5e40e8a6f3379dabd0389d39c8d2d98d62011a016916c8ace01e0711d4ce5e5cf3efbf3a4a42b9f9726ece6368fdc1e78056c70dfcbbcbc44a987820ce78e4024e962e4825b7226abfd75fdcdc1f88f1f67833fb8373a0fdd4743b5bbd1d6db55308699d28c72a03b4428bfc0a1f47865a68764c4b6d98e2b3b11ff9c6cd7d6c04686a1b89d5d76d9a9d6c3508d244ddd8f67392e1a8ac0372fbf1f98ffc404d76eb8da148eff88c0a6f3115c598efbe60c21139b3cc049e429d4ddb5f3c06e3rootrootrootrootrootrootrootrootrootrootrootrootpython-BTrees-4.7.2-bp155.2.10.src.rpmpython3-BTrees-develpython3-BTrees-devel(x86-64)    python3-BTreesrpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)4.7.23.0.4-14.6.0-14.0-15.2-14.14.3^^{G^[]c@]H@\`@Ycl@YNT@U>$TԬTomáš Chvátal Marketa Calabkova Marketa Calabkova Matej Cepl pgajdos@suse.comJohn Vandenberg jengelh@inai.dealoisio@gmx.combenoit.monin@gmx.frhpj@urpla.net- Do not bother with documentation - Update to 4.7.2: * Fix more cases of C and Python inconsistency.- update to 4.7.1 * Ensure the interface resolution order of all objects is consistent. See `issue 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``.- update to 4.6.1 * Add support for Python 3.8.- Replace %fdupes -s with plain %fdupes; hardlinks are better.- version update to 4.6.0 * Drop support for Python 3.4. * Fix tests against persistent 4.4. * Stop accidentally installing the 'terryfy' package in macOS wheels. See `issue 98 `_. * Fix segmentation fault in ``bucket_repr()``. See `issue 106 `_.- Update to v4.5.1 + Use pyproject.toml to specify build dependencies. This requires pip 18 or later to build from source. - 4.5.0 + Add support for Python 3.6 and 3.7, and drop support for Python 3.3. + Raise an ``ImportError`` consistently on Python 3 if the C extension for BTrees is used but the ``persistent`` C extension is not available. Previously this could result in an odd ``AttributeError``. + Fix the possibility of a rare crash in the C extension when deallocating items. + Respect the ``PURE_PYTHON`` environment variable at runtime even if the C extensions are available. + Always attempt to build the C extensions, but make their success optional. + Fix a ``DeprecationWarning`` that could come from I and L objects in Python 2 in pure-Python mode. - Use %license- Fix duplicate summaries- Update to version 4.4.1 * Fixed a packaging bug that caused extra files to be included (some of which caused problems in some platforms). 4.4.0: * Allow None as a special key (sorted smaller than all others). * This is a bit of a return to BTrees 3 behavior in that Nones are allowed as keys again. Other objects with default ordering are still not allowed as keys. 4.3.2: * Make the CPython implementation consistent with the pure-Python implementation and only check object keys for default comparison when setting keys. In Python 2 this makes it possible to remove keys that were added using a less restrictive version of BTrees. (In Python 3 keys that are unorderable still cannot be removed.) Likewise, all versions can unpickle trees that already had such keys. See: https://github.com/zopefoundation/BTrees/issues/53 and https://github.com/zopefoundation/BTrees/issues/51 * Make the Python implementation consistent with the CPython implementation and check object key identity before checking equality and performing comparisons. This can allow fixing trees that have keys that now have broken comparison functions. See https://github.com/zopefoundation/BTrees/issues/50 * Make the CPython implementation consistent with the pure-Python implementation and no longer raise TypeError for an object key (in object-keyed trees) with default comparison on __getitem__, get or in operations. Instead, the results will be a KeyError, the default value, and False, respectively. Previously, CPython raised a TypeError in those cases, while the Python implementation behaved as specified. * Likewise, non-integer keys in integer-keyed trees will raise KeyError, return the default and return False, respectively, in both implementations. Previously, pure-Python raised a KeyError, returned the default, and raised a TypeError, while CPython raised TypeError in all three cases. 4.3.1: * Packaging: fix password used to automate wheel creation on Travis. 4.3.0: * Fix unexpected OverflowError when passing 64bit values to long keys / values on Win64. See: https://github.com/zopefoundation/BTrees/issues/32 * When testing PURE_PYTHON environments under tox, avoid poisoning the user’s global wheel cache. * Ensure that the pure-Python implementation, used on PyPy and when a C compiler isn’t available for CPython, pickles identically to the C version. Unpickling will choose the best available implementation. This change prevents interoperability problems and database corruption if both implementations are in use. While it is no longer possible to pickle a Python implementation and have it unpickle to the Python implementation if the C implementation is available, existing Python pickles will still unpickle to the Python implementation (until pickled again). See: https://github.com/zopefoundation/BTrees/issues/19 * Avoid creating invalid objects when unpickling empty BTrees in a pure-Python environment. * Drop support for Python 2.6 and 3.2. 4.2.0: * Add support for Python 3.5. 4.1.4: * Ensure that pure-Python Bucket and Set objects have a human readable __repr__ like the C versions. 4.1.3: * Fix _p_changed when removing items from small pure-Python BTrees/TreeSets and when adding items to small pure-Python Sets. See: https://github.com/zopefoundation/BTrees/issues/13 - Converted to single-spec- update to version 4.1.2: * Suppress testing 64-bit values in OLBTrees on 32 bit machines. * Fix _p_changed for small pure-Python BTrees. - make the tests less verbose to avoid spamming the build log- version 4.1.1 - 4.1.1 (2014-12-27) Accomodate long values in pure-Python OLBTrees. - 4.1.0 (2014-12-26) Add support for PyPy and PyPy3. Add support for Python 3.4. BTree subclasses can define max_leaf_size or max_internal_size to control maximum sizes for Bucket/Set and BTree/TreeSet nodes. Detect integer overflow on 32-bit machines correctly under Python 3. Update pure-Python and C trees / sets to accept explicit None to indicate max / min value for minKey, maxKey. PR #3) Update pure-Python trees / sets to accept explicit None to indicate pen ranges for keys, values, items. (PR #3)lamb53 16847562814.7.2-bp155.2.104.7.2-bp155.2.10_compat.hfloatvaluemacros.hintkeymacros.hintvaluemacros.hobjectkeymacros.hobjectvaluemacros.h/usr/lib64/python3.6/site-packages/BTrees/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.opensuse.org/openSUSE:Backports:SLE-15-SP5/standard/17ded175975652afe9ca356c3b61e94a-python-BTreescpioxz5x86_64-suse-linuxC source, ASCII textASCII text)ή' Yutf-8f61ea51fe84084ccadc855ca99551ead6ac556b881f761d84c2003e5d4cfc24a?P7zXZ !t/6 ] crv(vX0EC |` h˛nGH!gyWt[ERXӐV _`!/ ]ϿxrMPR͜3c\03ԥ5g>srn)_ks/XP@yXֺ@x}b|&hA;a!@TD$ >!r@T^tHՁ.btX2fAs"LET~EAffnlu@źς?Xs " ]>?00~P*z̼!Z,JV:&<ę=aWSͻy~|]zTi#acD 7Pз;;I~rG/=@Z%܅}D~GZfK 3E Wr2.O,ݕ9#͕hcO ^ml7AVYg!-L_L \; a=JpygW><`}ր?4p_cKVG3XM’8WUFMjGh,`:ݞEyk(_/mXe;22DZFvsJo!Kx/[EzD\ Lؖn; oTz+]hǵ&|h]|3P%.Xodj) :iѽ]W>3V2%&ł}҅ztq6PsxQ@*Dzh;xqN~Dp_d& |~^pVo!2 Qd}.+p4BXMEŘ1f[T `RIkBKzvde\@6k%lvYOVe,E 7ܗ5mp2Y5'̈́{^KHGW >0PaڠHv__;Y 񣘉uJ#r/KS{h -S&YҸCΩ`݈VG~*Yf?Sj)){M~ʬ 2i+[G Ap9,)(B1wVvj+D10i+7Qd;KQ4ZAt}g>Bs6$m"8r*yȯk iI`7XqeИ>ߐ/F/ym#]d'ƣճHVQ2u9ۚ3ݩBܙ8JN9m5H 'xk@/t (t?#kRzC)8]rw W//dD3+c4%rµsEa5N"VfMտ_!~8*7d.V_0HMӔZ1E:4v٢G6;th??e僟PuZԷ$l:<D:c4ŷ64HP/s8M0c@JB[ C^{چ tI+joHSbK<0n!f+SG3Z)o.Vѝ@kV RSjD7JBuӰh/<)ػ[0=$wF .-s6\C5itJU[LO)I =( tķa8 zF_~KN $$U*BTᲀiVp* %f.Ctx `Ƞ8 <*m!} YZ