Hello community, here is the log from the commit of package python3-cffi for openSUSE:Factory checked in at 2015-11-02 12:55:49 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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-06-16 14:05:59.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python3-cffi.new/python3-cffi.changes 2015-11-02 12:55:50.000000000 +0100 @@ -1,0 +2,68 @@ +Sun Nov 1 19:29:10 UTC 2015 - [email protected] + +- update to 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... + +- changes from version 1.2.1: + * Nothing changed from v1.2.0. + +- 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. + +------------------------------------------------------------------- Old: ---- cffi-1.1.2.tar.gz New: ---- cffi-1.3.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-cffi.spec ++++++ --- /var/tmp/diff_new_pack.HKGPii/_old 2015-11-02 12:55:51.000000000 +0100 +++ /var/tmp/diff_new_pack.HKGPii/_new 2015-11-02 12:55:51.000000000 +0100 @@ -17,7 +17,7 @@ Name: python3-cffi -Version: 1.1.2 +Version: 1.3.0 Release: 0 Summary: Foreign Function Interface for Python calling C code License: MIT ++++++ cffi-1.1.2.tar.gz -> cffi-1.3.0.tar.gz ++++++ ++++ 6293 lines of diff (skipped)
