Hello community, here is the log from the commit of package python3-cffi for openSUSE:Factory checked in at 2015-06-02 10:04:06 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python3-cffi (Old) and /work/SRC/openSUSE:Factory/.python3-cffi.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python3-cffi" Changes: -------- --- /work/SRC/openSUSE:Factory/python3-cffi/python3-cffi.changes 2015-03-16 07:01:07.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.python3-cffi.new/python3-cffi.changes 2015-06-02 10:04:07.000000000 +0200 @@ -1,0 +2,55 @@ +Sun May 31 16:34:10 UTC 2015 - [email protected] + +- update to version 1.1.0: + * Out-of-line API mode: we can now declare integer types with + typedef int... foo_t;. The exact size and signness 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. + +------------------------------------------------------------------- +Sat May 30 03:24:13 UTC 2015 - [email protected] + +- specfile: + * tests need c++ compiler + +- update to version 1.0.3: + * Same as 1.0.2, apart from doc and test fixes on some platforms. + +- 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! + +- 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. + +- 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 + +------------------------------------------------------------------- Old: ---- cffi-0.9.2.tar.gz New: ---- cffi-1.1.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-cffi.spec ++++++ --- /var/tmp/diff_new_pack.yKMQIh/_old 2015-06-02 10:04:08.000000000 +0200 +++ /var/tmp/diff_new_pack.yKMQIh/_new 2015-06-02 10:04:08.000000000 +0200 @@ -17,7 +17,7 @@ Name: python3-cffi -Version: 0.9.2 +Version: 1.1.0 Release: 0 Summary: Foreign Function Interface for Python calling C code License: MIT @@ -30,6 +30,7 @@ # Documentation requirements: BuildRequires: python3-Sphinx # Test requirements: +BuildRequires: gcc-c++ BuildRequires: python3-pycparser BuildRequires: python3-pytest Requires: python3-pycparser ++++++ cffi-0.9.2.tar.gz -> cffi-1.1.0.tar.gz ++++++ ++++ 33552 lines of diff (skipped)
