Hello community, here is the log from the commit of package python-cffi for openSUSE:Factory checked in at 2016-01-15 10:39:04 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-cffi (Old) and /work/SRC/openSUSE:Factory/.python-cffi.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-cffi" Changes: -------- --- /work/SRC/openSUSE:Factory/python-cffi/python-cffi.changes 2015-09-24 07:16:09.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python-cffi.new/python-cffi.changes 2016-01-15 10:39:06.000000000 +0100 @@ -1,0 +2,71 @@ +Sat Jan 9 17:18:52 UTC 2016 - mich...@stroeder.com + +- 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... + +------------------------------------------------------------------- Old: ---- cffi-1.2.1.tar.gz New: ---- cffi-1.4.2.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-cffi.spec ++++++ --- /var/tmp/diff_new_pack.49hc5r/_old 2016-01-15 10:39:07.000000000 +0100 +++ /var/tmp/diff_new_pack.49hc5r/_new 2016-01-15 10:39:07.000000000 +0100 @@ -17,7 +17,7 @@ Name: python-cffi -Version: 1.2.1 +Version: 1.4.2 Release: 0 Summary: Foreign Function Interface for Python calling C code License: MIT ++++++ cffi-1.2.1.tar.gz -> cffi-1.4.2.tar.gz ++++++ ++++ 7542 lines of diff (skipped)
