Changelog for
python38-cffi-1.15.1-1.1.x86_64.rpm :
* Tue Jul 19 2022 Dirk Müller
- update to 1.15.1:
* If you call ffi.embedding_api() but don’t write any extern “Python” function there, then the resulting C code would fail an assert. Fixed.
* Updated Windows/arm64 embedded libffi static lib to v3.4.2, and scripted to ease future updates (thanks Niyas Sait!)
* Sat Nov 06 2021 Dirk Müller - update to 1.15.0:
* Fixed MANIFEST.in to include missing file for Windows arm64 support
* Fixed Linux wheel build to use gcc default ISA for libffi
* Updated setup.py Python trove specifiers to currently-tested Python versions
* CPython 3.10 support (including wheels)
* MacOS arm64 support (including wheels)
* Initial Windows arm64 support
* Misc. doc and test updates
* Fri Jul 16 2021 Dirk Müller - update to 1.14.6:
* Revert \"grovel: detect :float and :double in the :auto type\"
* Fri Feb 12 2021 Dirk Müller - update to 1.14.5:
* Source fix for old gcc versions
* Sat Dec 19 2020 Dirk Müller - update to 1.14.4:
* no upstream changelog provided
* Mon Sep 28 2020 Dirk Mueller - update to 1.14.3:
* no upstream changelog provided
* Thu Aug 20 2020 Ondřej Súkup - update to 1.14.2
* CPython 3 on Windows: we again try to compile with Py_LIMITED_API by default
* Mon Aug 10 2020 Dirk Mueller - update to 1.14.1:
* CFFI source code is now hosted on Heptapod.
* Improved support for typedef int my_array_t[...]; with an explicit dot-dot-dot in API mode (issue #453)
* Windows (32 and 64 bits): multiple fixes for ABI-mode call to functions that return a structure.
* Experimental support for MacOS 11 on aarch64.
* and a few other minor changes and bug fixes.
* Mon Feb 24 2020 Ondřej Súkup - Update to 1.14.0
* ffi.dlopen() can now be called with a handle (as a void
*) to an already-opened C library.
* fixed a stack overflow issue for calls like lib.myfunc([large list]).
* fixed a memory leak inside ffi.getwinerror() on CPython 3.x.
* Mon Nov 18 2019 Todd R - Update to 1.13.2:
* re-release because the Linux wheels came with an attached version of libffi that was very old and buggy- Update to 1.13.1:
* deprecate the way to declare in cdef() a global variable with only void
*foo;. You should always use a storage class, like extern void
*foo; or maybe static void
*foo;. These are all equivalent for the purposes of cdef(), but the reason for deprecating the bare version is that (as far as I know) it would always be mistake in a real C header.
* fix the regression RuntimeError: found a situation in which we try to build a type recursively.
* fixed issue #427 where a multithreading mistake in the embedding logic initialization code would cause deadlocks on CPython 3.7.
* Tue Oct 15 2019 Tomáš Chvátal - Update to 1.13.0:
* No changelog provided upstream
* Tue Apr 30 2019 Todd R - Update to 1.12.3
* Fix for nested struct types that end in a var-sized array (#405).
* Add support for using U and L characters at the end of integer constants in ffi.cdef() (thanks Guillaume).
* More 3.8 fixes.
* Thu Mar 07 2019 John Vandenberg - Remove test suite exception which was fixed by 7a76a38153
*.patch- Add doc/
*/
*.rst to %doc
* Sat Mar 02 2019 Ondřej Súkup - update to 1.12.3- drop patches: 3184b0a675fc425b821b528d7fdf744b2f08dadf.patch 7a76a381534012af4790e815140d1538510b7d93.patch e2e324a2f13e3a646de6f6ff03e90ed7d37e2636.patch
* Direct support for pkg-config.
* ffi.from_buffer() takes a new optional first argument that gives the array type of the result. It also takes an optional keyword argument require_writable to refuse read-only Python buffers.
* ffi.new(), ffi.gc() or ffi.from_buffer() cdata objects can now be released at known times, either by using the with keyword or by calling the new ffi.release().
* Accept an expression like ffi.new(\"int[4]\", p) if p is itself another cdata int[4].
* CPython 2.x: ffi.dlopen() failed with non-ascii file names on Posix
* CPython: if a thread is started from C and then runs Python code (with callbacks or with the embedding solution), then previous versions of cffi would contain possible crashes and/or memory leaks.
* Support for ffi.cdef(..., pack=N) where N is a power of two.
* Mon Oct 29 2018 mceplAATTsuse.com- Add 7a76a381534012af4790e815140d1538510b7d93.patch to fix bsc#1111657 (we need use to proper void returning function not to corrupt memory in tests).
* Wed Oct 17 2018 mceplAATTsuse.com- Fix calling of py.test executor.
* Fri Sep 21 2018 mceplAATTsuse.com- Add 3184b0a675fc425b821b528d7fdf744b2f08dadf.patch as a workaround against https://bitbucket.org/cffi/cffi/issues/378/ (possible bug in GCC, see https://bugzilla.redhat.com/1552724).
* Wed Sep 19 2018 mceplAATTsuse.com- Remove ignore-tests.patch -- testing what will happen- Add e2e324a2f13e3a646de6f6ff03e90ed7d37e2636.patch from upstream to remove some warnings.
* Tue Sep 18 2018 Matěj Cepl - Switch off falling tests with new patch ignore-tests.patch instead of -k parameter for py.test. https://bitbucket.org/cffi/cffi/issues/384/
* Fri Mar 02 2018 arunAATTgmx.de- update to version 1.11.5:
* Issue #357: fix ffi.emit_python_code() which generated a buggy Python file if you are using a struct with an anonymous union field or vice-versa.
* Windows: ffi.dlopen() should now handle unicode filenames.
* ABI mode: implemented ffi.dlclose() for the in-line case (it used to be present only in the out-of-line case).
* Fixed a corner case for setup.py install --record=xx --root=yy with an out-of-line ABI module. Also fixed Issue #345.
* More hacks on Windows for running CFFI’s own setup.py.
* Issue #358: in embedding, to protect against (the rare case of) Python initialization from several threads in parallel, we have to use a spin-lock. On CPython 3 it is worse because it might spin-lock for a long time (execution of Py_InitializeEx()). Sadly, recent changes to CPython make that solution needed on CPython 2 too.
* CPython 3 on Windows: we no longer compile with Py_LIMITED_API by default because such modules cannot be used with virtualenv. Issue [#350] mentions a workaround if you still want that and are not concerned about virtualenv: pass a define_macros=[(\"Py_LIMITED_API\", None)] to the ffibuilder.set_source() call.
* Tue Feb 20 2018 arunAATTgmx.de- specfile:
* delete patch cffi-loader.patch; included upstream- update to version 1.11.4:
* Windows: reverted linking with python3.dll, because virtualenv does not make this DLL available to virtual environments for now. See Issue #355. On Windows only, the C extension modules created by cffi follow for now the standard naming scheme foo.cp36-win32.pyd, to make it clear that they are regular CPython modules depending on python36.dll.- changes from version 1.11.3:
* Fix on CPython 3.x: reading the attributes __loader__ or __spec__ from the cffi-generated lib modules gave a buggy SystemError. (These attributes are always None, and provided only to help compatibility with tools that expect them in all modules.)
* More Windows fixes: workaround for MSVC not supporting large literal strings in C code (from ffi.embedding_init_code(large_string)); and an issue with Py_LIMITED_API linking with python35.dll/python36.dll instead of python3.dll.
* Small documentation improvements.
* Thu Jan 18 2018 tchvatalAATTsuse.com- Add patch cffi-loader.patch to fix bsc#1070737- Sort out with spec-cleaner
