python311-cffi-1.15.1-150400.8.7.2<>,Lf0Mp9|' +U4i4ï0_[FH ‹g)E uȧlQKɟvQ2:M%:ǽ^`rV`WZA1 7)??lW`s$Ee_Ru U%'3h<~YH{m(0V*tYlܳ!غOݤ,Θأ,D!/J 岾Y2[hGoQ/T!l֊Džկ]jB\}@g9>>?d % Z!BF \hOO nO  O HO O hOO/OO H (!8!)9!):$)FGOHDOIOXY\O]<O^fbcOdefluOv0wOxLOy?zCpython311-cffi1.15.1150400.8.7.2Foreign Function Interface for Python calling C codeForeign Function Interface for Python calling C code. The aim of this project is to provide a convenient and reliable way of calling C code from Python.f0Mh04-ch1cSUSE Linux Enterprise 15SUSE LLC MIThttps://www.suse.com/Unspecifiedhttps://cffi.readthedocs.orglinuxx86_64H_LK TT M M..44^^$$^^1~1~ݪݪFFD9EP\ mUXV"8h<+ X EyY.1 AA큤A큤A큤A큤f0tf0sf0tf0sf0sf0sf0sf0sf0sf0sbѓf0tf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sf0sbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓf0Lbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓbѓf0Lbѓ6f26a8a3a3b40b99d4c7af0784dbe053625e981bbef9c87b98c55403a84a083ee02689d10f44f4054629449c78a5e78a896bd2990f16572f2180cbb79382196c8935213bbeeb64ca411d1a633513c53b1936baa808d703aef8aedabc88b8016c01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546bcba8d3c67c9eb8b9cbf9725c0eff2e30bde7eb0c98886460f0c4e9fd0189f47a01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b73e94f712ef82fff0aa07ec813a3d0179a1fca2ad140d57856191b48520f7963ac4ed6477ad97cd2b1588f7e8e7ea1b0708097b303901f859ae41bc568c57a14eb107fb5a7c6be184ce57be3d0ebdade83c2d921215652d310e6d52e76b37a230a68c0369f73d13c0f2c9cd9793526ede2e7b745ad06036b964f5cd1c99061df0a68c0369f73d13c0f2c9cd9793526ede2e7b745ad06036b964f5cd1c99061df629dd31d5cac625316f3ca9ea63de7b4b92d9cb86ce5664d3d3292d8d3dab8a3629dd31d5cac625316f3ca9ea63de7b4b92d9cb86ce5664d3d3292d8d3dab8a3cd0e8e8d4c176f08763ff7c8b96bfeca3045cf4b22ab1279bd802b51fa435b47cd0e8e8d4c176f08763ff7c8b96bfeca3045cf4b22ab1279bd802b51fa435b47a349106fcad4e3c8d4bd432ba854675d2031a22470482141afddc6e13f7ffefca349106fcad4e3c8d4bd432ba854675d2031a22470482141afddc6e13f7ffefc6f7692b7a9aa1abd487e596ec3b797b6831a3a3743857a6c289074a2b7e86e9f6f7692b7a9aa1abd487e596ec3b797b6831a3a3743857a6c289074a2b7e86e9f56c91b7251666b3f03b4c84b3b24c9001110ed25e09199d89d7f864416dcc56c56c91b7251666b3f03b4c84b3b24c9001110ed25e09199d89d7f864416dcc56cb0e2356b6b7fbbfa381ed8417d1424a6efd1c6b4898cc94f63f776be50affac1b0e2356b6b7fbbfa381ed8417d1424a6efd1c6b4898cc94f63f776be50affac1b250382a989285cc80d85fd2e2c76e5f03ed630d6f4a18d31665863969f7e9f1b250382a989285cc80d85fd2e2c76e5f03ed630d6f4a18d31665863969f7e9f14e9888dbac190160f14e94b3195acc55cc4af2fea4fd1fa9571012c2235f15f34e9888dbac190160f14e94b3195acc55cc4af2fea4fd1fa9571012c2235f15f3a6748be232c1cd1b0caa587b59aa4c51895996b52fee1eaedffb47296e6168bea6748be232c1cd1b0caa587b59aa4c51895996b52fee1eaedffb47296e6168bece69c8b16c250ec30270fe953918ed948ecafc524853a41fa5275a42a618f654ce69c8b16c250ec30270fe953918ed948ecafc524853a41fa5275a42a618f65429fcc79ad00ea3c24f28fefcd87c15c0478085d8c094d43a70eec920b3bd575129fcc79ad00ea3c24f28fefcd87c15c0478085d8c094d43a70eec920b3bd5751cc65e75af12d95319c16bdc3939a710b2d692fa9d4a8a728e729fef9bdd99b4acc65e75af12d95319c16bdc3939a710b2d692fa9d4a8a728e729fef9bdd99b4a3ffbb355f998bbc0aa4d7db1589fe82614d115d11b7053873d2ec7e6d83b0fbb3ffbb355f998bbc0aa4d7db1589fe82614d115d11b7053873d2ec7e6d83b0fbbedfa92b6901e2086db30b32b09e0d17dd6278bfe89e6dd806abecb097a417910edfa92b6901e2086db30b32b09e0d17dd6278bfe89e6dd806abecb097a417910681b5fc6ac0b19762b12c33b6589cd351508efdf61050e8974ed6e349ebf3afc681b5fc6ac0b19762b12c33b6589cd351508efdf61050e8974ed6e349ebf3afccd05edeee47f9bc8145be7c8da1260d0aa129091705eff111949040d9d7bedd4b4a9c0d6b752a0f1e9db71670cbd660c6c05a3e523e9f5df03abc0ea47281147f6d9e3178e104686d1f33d051aa02601963ec0c48139a7b54943ea1dc728c2a7cb125a94878f6ebd66cff5b1007a244b0c8fe4255875ee389be9e89479db24da879648ccb73a0455579c6c9cf713ea656512eea1b2ef21520ea5deebc49af33ebfd45d0ffa2f03cac2b6ab02f7922f922e55ebaeeb00e84682cddf6f6abdc693412e2ec420c8ec986d4f28e1d61967080fa0ca799ab335b125a4512c69096b50aceff5a442d1c35808d431359b8822da293924c7e9c68b800022d7a513e55440bfac53892e14d24bc3732e21fc10d1a39bf7f5942e8fe20c4582efe444dd759b1cc5ea47c92cdb0b5db0dc46696a50fcfcaa22fb62ba8b3fbdfd6a282cbe730897d4d37703083298ba8c39091a742013d72f4c847b0809ed209afc1061edde96fc61ff505d519fdbc2e00be68099baaa3ed15175c6ddea8a3dcf1b3f1c7204a139dc107f033d92dababe5081e377b11509b10c1b63d8c04d74af0b625d79b63c2cfd70eef996be62b0caa2da535676e3714e58635032b80c519aef805b8e95ca6205584e1d82ad72286e8faf324eff2bd9b001775dfcba81e3e21b600050e3cf454475ecde5ff20a624010655cbdf83fd16d3aed6684721a01fdd62658394b8262094df184be51a1c4bf6936731828b4d584f3b7475f6d3eebc1322a888a5180e5d5fbb350d4ea94c138c23aa13567ffc0679abbbf963f77d81e9be2fdbd1e58112c2e5d65ed5eb2846a008abde2d10e31732cd0b268a76a02002529111cca16a29cc7c1d92b4e2177efda0d66b3f760ee633a3cc645c51a6d404881ba36373a9c3f38abca381a99289c454d97f6f9bf23ee052a527ae40aada700685bfb02a88a2662670ac7d5cf011fb383c09b71396d74dc632998613c3b86b289f4bf0cb99ff57dc63f8efc0018e0ffb09edd9135cb16541813f3efce26a84f6cc9567ab4e5de5072ad046dcbffccb15f4e11a0246d28926feee26f13ab7e5f49e79b3b3248baee0a05cd72cb493e741da97753af0b1658b0b8ddbab21d4c48c6f5a4c42144e0f0adf0a6333506c716d9b0b9a0e71ac36e73d6e7592013235f0497c68649cb1fd71bb519b2cf41203656658c7cd66599f910b8464740f6989e66cd9c10e0b1e369420baf2a848a1a9125b5047166dd1a774de21e0005b766c92f840781ee944b87173d2358cb3d5f562a212d80d4bab4de1292e3dc9dd905a7003cc45e3a61ec7dd54777a686fa3ff10fe3d4281d322ff957d372236078d053103fee1b8186a8d974f80a70076a00629cc4bd0ac7abeacac501a66e3f17a17fe9ab962812456354090e1bbd835c41a6f1ef63f5f20212adf41db517c28f11e6a225e46a7804b80f5b077bbed68808cfebadeb5e3523f2a8c9a96495c587bd96df1eac2a33rootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootrootpython-cffi-1.15.1-150400.8.7.2.src.rpmpython311-cffipython311-cffi(x86-64)@@@@@@@@@@@@@@@     ld-linux-x86-64.so.2()(64bit)ld-linux-x86-64.so.2(GLIBC_2.3)(64bit)libc.so.6()(64bit)libc.so.6(GLIBC_2.14)(64bit)libc.so.6(GLIBC_2.2.5)(64bit)libc.so.6(GLIBC_2.3)(64bit)libc.so.6(GLIBC_2.3.4)(64bit)libc.so.6(GLIBC_2.4)(64bit)libc.so.6(GLIBC_2.7)(64bit)libffi.so.7()(64bit)libffi.so.7(LIBFFI_BASE_7.0)(64bit)libffi.so.7(LIBFFI_CLOSURE_7.0)(64bit)libpthread.so.0()(64bit)libpthread.so.0(GLIBC_2.2.5)(64bit)python(abi)python311-pycparserrpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PartialHardlinkSets)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)3.113.0.4-14.6.0-14.0.4-14.0-15.2-14.14.3dBzd7c @c@b֜an@`t`&m_@_q@_>e_16^S]҇]\8\\zp@[@[$@[@[:@[Z compares equal to 42 and compares equal to b'A'. Unlike C, does not compare equal to ffi.cast("unsigned int", -1): it compares smaller, because -1 < 4294967295. * PyPy: ffi.new() and ffi.new_allocator()() did not record “memory pressure”, causing the GC to run too infrequently if you call ffi.new() very often and/or with large arrays. Fixed in PyPy 5.7. * Support in ffi.cdef() for numeric expressions with + or -. Assumes that there is no overflow; it should be fixed first before we add more general support for arbitrary arithmetic on constants.- do not generate HTML documentation for packages that are indirect dependencies of Sphinx (see docs at https://cffi.readthedocs.org/ )- update to 1.9.1 - Structs with variable-sized arrays as their last field: now we track the length of the array after ffi.new() is called, just like we always tracked the length of ffi.new("int[]", 42). This lets us detect out-of-range accesses to array items. This also lets us display a better repr(), and have the total size returned by ffi.sizeof() and ffi.buffer(). Previously both functions would return a result based on the size of the declared structure type, with an assumed empty array. (Thanks andrew for starting this refactoring.) - Add support in cdef()/set_source() for unspecified-length arrays in typedefs: typedef int foo_t[...];. It was already supported for global variables or structure fields. - I turned in v1.8 a warning from cffi/model.py into an error: 'enum xxx' has no values explicitly defined: refusing to guess which integer type it is meant to be (unsigned/signed, int/long). Now I’m turning it back to a warning again; it seems that guessing that the enum has size int is a 99%-safe bet. (But not 100%, so it stays as a warning.) - Fix leaks in the code handling FILE * arguments. In CPython 3 there is a remaining issue that is hard to fix: if you pass a Python file object to a FILE * argument, then os.dup() is used and the new file descriptor is only closed when the GC reclaims the Python file object—and not at the earlier time when you call close(), which only closes the original file descriptor. If this is an issue, you should avoid this automatic convertion of Python file objects: instead, explicitly manipulate file descriptors and call fdopen() from C (...via cffi). - When passing a void * argument to a function with a different pointer type, or vice-versa, the cast occurs automatically, like in C. The same occurs for initialization with ffi.new() and a few other places. However, I thought that char * had the same property—but I was mistaken. In C you get the usual warning if you try to give a char * to a char ** argument, for example. Sorry about the confusion. This has been fixed in CFFI by giving for now a warning, too. It will turn into an error in a future version. - Issue #283: fixed ffi.new() on structures/unions with nested anonymous structures/unions, when there is at least one union in the mix. When initialized with a list or a dict, it should now behave more closely like the { } syntax does in GCC. - CPython 3.x: experimental: the generated C extension modules now use the “limited API”, which means that, as a compiled .so/.dll, it should work directly on any version of CPython >= 3.2. The name produced by distutils is still version-specific. To get the version-independent name, you can rename it manually to NAME.abi3.so, or use the very recent setuptools 26. - Added ffi.compile(debug=...), similar to python setup.py build --debug but defaulting to True if we are running a debugging version of Python itself. - Removed the restriction that ffi.from_buffer() cannot be used on byte strings. Now you can get a char * out of a byte string, which is valid as long as the string object is kept alive. (But don’t use it to modify the string object! If you need this, use bytearray or other official techniques.) - PyPy 5.4 can now pass a byte string directly to a char * argument (in older versions, a copy would be made). This used to be a CPython-only optimization. - ffi.gc(p, None) removes the destructor on an object previously created by another call to ffi.gc() - bool(ffi.cast("primitive type", x)) now returns False if the value is zero (including -0.0), and True otherwise. Previously this would only return False for cdata objects of a pointer type when the pointer is NULL. - bytearrays: ffi.from_buffer(bytearray-object) is now supported. (The reason it was not supported was that it was hard to do in PyPy, but it works since PyPy 5.3.) To call a C function with a char * argument from a buffer object—now including bytearrays—you write lib.foo(ffi.from_buffer(x)). Additionally, this is now supported: p[0:length] = bytearray-object. The problem with this was that a iterating over bytearrays gives numbers instead of characters. (Now it is implemented with just a memcpy, of course, not actually iterating over the characters.) - C++: compiling the generated C code with C++ was supposed to work, but failed if you make use the bool type (because that is rendered as the C _Bool type, which doesn’t exist in C++). - help(lib) and help(lib.myfunc) now give useful information, as well as dir(p) where p is a struct or pointer-to-struct. - drop upstreamed python-cffi-avoid-bitshifting-negative-int.patch- update for multipython build- Add python-cffi-avoid-bitshifting-negative-int.patch to actually fix the "negative left shift" warning by replacing bitshifting in appropriate places by bitwise and comparison to self; patch taken from upstream git. Drop cffi-1.5.2-wnoerror.patch: no longer required.- disable "negative left shift" warning in test suite to prevent failures with gcc6, until upstream fixes the undefined code in question (boo#981848, cffi-1.5.2-wnoerror.patch)- Update to version 1.6.0: * ffi.list_types() * ffi.unpack() * extern “Python+C” * in API mode, lib.foo.__doc__ contains the C signature now. * Yet another attempt at robustness of ffi.def_extern() against CPython’s interpreter shutdown logic.- update to 1.5.2 * support for cffi-based embedding * more robustness for shutdown logic- update to version 1.4.2: * Nothing changed from v1.4.1. - changes from version 1.4.1: * Fix the compilation failure of cffi on CPython 3.5.0. (3.5.1 works; some detail changed that makes some underscore-starting macros disappear from view of extension modules, and I worked around it, thinking it changed in all 3.5 versions—but no: it was only in 3.5.1.) - changes from version 1.4.0: * A better way to do callbacks has been added (faster and more portable, and usually cleaner). It is a mechanism for the out-of-line API mode that replaces the dynamic creation of callback objects (i.e. C functions that invoke Python) with the static declaration in cdef() of which callbacks are needed. This is more C-like, in that you have to structure your code around the idea that you get a fixed number of function pointers, instead of creating them on-the-fly. * ffi.compile() now takes an optional verbose argument. When True, distutils prints the calls to the compiler. * ffi.compile() used to fail if given sources with a path that includes "..". Fixed. * ffi.init_once() added. See docs. * dir(lib) now works on libs returned by ffi.dlopen() too. * Cleaned up and modernized the content of the demo subdirectory in the sources (thanks matti!). * ffi.new_handle() is now guaranteed to return unique void * values, even if called twice on the same object. Previously, in that case, CPython would return two cdata objects with the same void * value. This change is useful to add and remove handles from a global dict (or set) without worrying about duplicates. It already used to work like that on PyPy. This change can break code that used to work on CPython by relying on the object to be kept alive by other means than keeping the result of ffi.new_handle() alive. (The corresponding warning in the docs of ffi.new_handle() has been here since v0.8!) - changes from version 1.3.1: * The optional typedefs (bool, FILE and all Windows types) were not always available from out-of-line FFI objects. * Opaque enums are phased out from the cdefs: they now give a warning, instead of (possibly wrongly) being assumed equal to unsigned int. Please report if you get a reasonable use case for them. * Some parsing details, notably volatile is passed along like const and restrict. Also, older versions of pycparser mis-parse some pointer-to-pointer types like char * const *: the “const” ends up at the wrong place. Added a workaround. - changes from version 1.3.0: * Added ffi.memmove(). * Pull request #64: out-of-line API mode: we can now declare floating-point types with typedef float... foo_t;. This only works if foo_t is a float or a double, not long double. * Issue #217: fix possible unaligned pointer manipulation, which crashes on some architectures (64-bit, non-x86). * Issues #64 and #126: when using set_source() or verify(), the const and restrict keywords are copied from the cdef to the generated C code; this fixes warnings by the C compiler. It also fixes corner cases like typedef const int T; T a; which would previously not consider a as a constant. (The cdata objects themselves are never const.) * Win32: support for __stdcall. For callbacks and function pointers; regular C functions still don’t need to have their calling convention declared. * Windows: CPython 2.7 distutils doesn’t work with Microsoft’s official Visual Studio for Python, and I’m told this is not a bug. For ffi.compile(), we removed a workaround that was inside cffi but which had unwanted side-effects. Try saying import setuptools first, which patches distutils...- Update to version 1.2.1 * No changes entry for this version - Changes from version 1.2.0 * Out-of-line mode: ``int a[][...];`` can be used to declare a structure field or global variable which is, simultaneously, of total length unknown to the C compiler (the ``a[]`` part) and each element is itself an array of N integers, where the value of N *is * known to the C compiler (the ``int`` and ``[...]`` parts around it). Similarly, ``int a[5][...];`` is supported (but probably less useful: remember that in C it means ``int (a[5])[...];``). * PyPy: the ``lib.some_function`` objects were missing the attributes ``__name__``, ``__module__`` and ``__doc__`` that are expected e.g. by some decorators-management functions from ``functools``. * Out-of-line API mode: you can now do ``from _example.lib import x`` to import the name ``x`` from ``_example.lib``, even though the ``lib`` object is not a standard module object. (Also works in ``from _example.lib import *``, but this is even more of a hack and will fail if ``lib`` happens to declare a name called ``__all__``. Note that `` *`` excludes the global variables; only the functions and constants make sense to import like this.) * ``lib.__dict__`` works again and gives you a copy of the dict---assuming that ``lib`` has got no symbol called precisely ``__dict__``. (In general, it is safer to use ``dir(lib)``.) * Out-of-line API mode: global variables are now fetched on demand at every access. It fixes issue #212 (Windows DLL variables), and also allows variables that are defined as dynamic macros (like ``errno``) or ``__thread`` -local variables. (This change might also tighten the C compiler's check on the variables' type.) * Issue #209: dereferencing NULL pointers now raises RuntimeError instead of segfaulting. Meant as a debugging aid. The check is only for NULL: if you dereference random or dead pointers you might still get segfaults. * Issue #152: callbacks__: added an argument ``ffi.callback(..., onerror=...)``. If the main callback function raises an exception and ``onerror`` is provided, then ``onerror(exception, exc_value, traceback)`` is called. This is similar to writing a ``try: except:`` in the main callback function, but in some cases (e.g. a signal) an exception can occur at the very start of the callback function---before it had time to enter the ``try: except:`` block. * Issue #115: added ``ffi.new_allocator()``, which officializes support for `alternative allocators`__. .. __: using.html#callbacks .. __: using.html#alternative-allocators- update to version 1.1.0 (fate#318838): * Out-of-line API mode: we can now declare integer types with typedef int... foo_t;. The exact size and signedness of foo_t is figured out by the compiler. * Out-of-line API mode: we can now declare multidimensional arrays (as fields or as globals) with int n[...][...]. Before, only the outermost dimension would support the ... syntax. * Out-of-line ABI mode: we now support any constant declaration, instead of only integers whose value is given in the cdef. Such “new” constants, i.e. either non-integers or without a value given in the cdef, must correspond to actual symbols in the lib. At runtime they are looked up the first time we access them. This is useful if the library defines extern const sometype somename;. * ffi.addressof(lib, "func_name") now returns a regular cdata object of type “pointer to function”. You can use it on any function from a library in API mode (in ABI mode, all functions are already regular cdata objects). To support this, you need to recompile your cffi modules. * Issue #198: in API mode, if you declare constants of a struct type, what you saw from lib.CONSTANT was corrupted. * Issue #196: ffi.set_source("package._ffi", None) would incorrectly generate the Python source to package._ffi.py instead of package/_ffi.py. Also fixed: in some cases, if the C file was in build/foo.c, the .o file would be put in build/build/foo.o. - additional changes from version 1.0.3: * Same as 1.0.2, apart from doc and test fixes on some platforms - additional changes from version 1.0.2: * Variadic C functions (ending in a ”...” argument) were not supported in the out-of-line ABI mode. This was a bug—there was even a (non-working) example doing exactly that! - additional changes from version 1.0.1: * ffi.set_source() crashed if passed a sources=[..] argument. Fixed by chrippa on pull request #60. * Issue #193: if we use a struct between the first cdef() where it is declared and another cdef() where its fields are defined, then this definition was ignored. * Enums were buggy if you used too many ”...” in their definition - additional changes from version 1.0.0: * The main news item is out-of-line module generation: + for ABI level, with ffi.dlopen() + for API level, which used to be with ffi.verify(), now deprecated - add python-cffi-rpmlintrc: cffi specifically installs C headers in site-packages - add new test dependency gcc-c++ - skip the tests on SLE11 since they fail on i586- Update to 0.9.2 * No upstream changelog See https://bitbucket.org/cffi/cffi/commits/all for a list of commitsh04-ch1c 1714484045 !!##%%''))++-./0123456789:;<=>?@ABCDEFGHIJKLMNO1.15.1-150400.8.7.21.15.1-150400.8.7.2_cffi_backend.cpython-311-x86_64-linux-gnu.socfficffi-1.15.1-py3.11.egg-infoPKG-INFOSOURCES.txtdependency_links.txtentry_points.txtnot-zip-saferequires.txttop_level.txt__init__.py__pycache____init__.cpython-311.opt-1.pyc__init__.cpython-311.pycapi.cpython-311.opt-1.pycapi.cpython-311.pycbackend_ctypes.cpython-311.opt-1.pycbackend_ctypes.cpython-311.pyccffi_opcode.cpython-311.opt-1.pyccffi_opcode.cpython-311.pyccommontypes.cpython-311.opt-1.pyccommontypes.cpython-311.pyccparser.cpython-311.opt-1.pyccparser.cpython-311.pycerror.cpython-311.opt-1.pycerror.cpython-311.pycffiplatform.cpython-311.opt-1.pycffiplatform.cpython-311.pyclock.cpython-311.opt-1.pyclock.cpython-311.pycmodel.cpython-311.opt-1.pycmodel.cpython-311.pycpkgconfig.cpython-311.opt-1.pycpkgconfig.cpython-311.pycrecompiler.cpython-311.opt-1.pycrecompiler.cpython-311.pycsetuptools_ext.cpython-311.opt-1.pycsetuptools_ext.cpython-311.pycvengine_cpy.cpython-311.opt-1.pycvengine_cpy.cpython-311.pycvengine_gen.cpython-311.opt-1.pycvengine_gen.cpython-311.pycverifier.cpython-311.opt-1.pycverifier.cpython-311.pyc_cffi_errors.h_cffi_include.h_embedding.hapi.pybackend_ctypes.pycffi_opcode.pycommontypes.pycparser.pyerror.pyffiplatform.pylock.pymodel.pyparse_c_type.hpkgconfig.pyrecompiler.pysetuptools_ext.pyvengine_cpy.pyvengine_gen.pyverifier.pypython311-cffiREADME.mdcdef.rstdesign.rstembedding.rstgoals.rstgrant-cffi-1.0.rstindex.rstinstallation.rstoverview.rstparse_c_type.rstref.rstusing.rstwhatsnew.rstpython311-cffiLICENSE/usr/lib64/python3.11/site-packages//usr/lib64/python3.11/site-packages/cffi-1.15.1-py3.11.egg-info//usr/lib64/python3.11/site-packages/cffi//usr/lib64/python3.11/site-packages/cffi/__pycache__//usr/share/doc/packages//usr/share/doc/packages/python311-cffi//usr/share/licenses//usr/share/licenses/python311-cffi/-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.suse.de/SUSE:Maintenance:33601/SUSE_SLE-15-SP4_Update/45c2737bfb4ef47cababe2a20a6bf402-python-cffi.SUSE_SLE-15-SP4_Updatedrpmxz5x86_64-suse-linuxELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=8210ed58af4119bdb7cff85d52e45fe3c2e9947a, strippeddirectoryASCII textPython script, ASCII text executableC source, ASCII text !"#$%&'()*+,-./0123456789:;<=>RRR R R RRRRRRR R RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR `>Uutf-8c7e6571151e0114fd24c2b63f63db17cbe9400b6f062c1803a798eb049c89441? 7zXZ !t/]"k%4Pa I_t0򸦠I?w'B`f &̀T8QI> O^[ӣ&Map23 "s@C$-,[?:ds|44f1m%[e{6 Ґѝ?o*q8 ~UoRO-;UFIfĹLTv]R…o?E!5AOQe#Bw.WX̎td<C2猋$`gRd&V~GOY[J ?ӟ:e mXctH*--l<8rےX˩"&%avb+>} nbwimRs|BF,<nz&[UH/5łJtpir>#}g"qET?Q.R!އAf얏^2 &hɗs;ùm]@;CNy;LöZtM۩bFݰ~:c]1}oXx-:Tph1Qر=d5ӤױOJ|ZHiIGw/d_Ic!GXKh'ihP-[6ﳟ5I8 ]j7tG|j~Nޏ7yuuU@]N^V'~%7(nБgC Z( &N^E(:OĦ6z>K.t _"IVX"'-(a@ztng"Df.{6hUL4/q<9U\LuQ&Km DPDzqD2?_"64iM؂c Nf`#czQ؈͏p}1)y1zhel8 "2.>:~l7h0' ${.\)P)h#{Do3kՖ%XbWD QԛD+5"/uxNW:p.iO0TPu?/&]jP7 v$/\i[t3]C)WCU>@ŭ(*7^;|3\^USYO ۢ ܅H$m'fn~hQE2Q6o/N^m`y&-YLXNd#F.Sّ8l}"TP%y@Y|zW'Re[ԍQmtQf^7!+T5Wrw.! [s0gq0ؽW (瑟DBӈ ZPGXsjH'Fz9?YR ˗ ֦-0&Is#Lk*}? 8lzrܵMd5d-8(3Z0ʮܻmH!~3zCހj4]Z\;ZgjO~nGMrWB=Yb͢hn9/W\SJ) 3T=R<\ޟ2M`Haq?ȇG eׅ?Sm@l:fGqe\.Q,U`n|μ6fSC~ʝŸu>`)Pzv ~!XGN/bnhUxtq[?޻