Hello community,

here is the log from the commit of package python-cffi for openSUSE:Factory 
checked in at 2017-07-04 11:56:44
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-cffi (Old)
 and      /work/SRC/openSUSE:Factory/.python-cffi.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-cffi"

Tue Jul  4 11:56:44 2017 rev:16 rq:507344 version:1.10.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-cffi/python-cffi.changes  2017-04-19 
18:03:56.292298503 +0200
+++ /work/SRC/openSUSE:Factory/.python-cffi.new/python-cffi.changes     
2017-07-04 11:56:45.787142379 +0200
@@ -1,0 +2,45 @@
+Thu Jun 29 16:03:46 UTC 2017 - tbecht...@suse.com
+
+- update to 1.10.0:
+ * Issue #295: use calloc() directly instead of PyObject_Malloc()+memset()
+   to handle ffi.new() with a default allocator. Speeds up ffi.new(large-array)
+   where most of the time you never touch most of the array.
+  * Some OS/X build fixes (“only with Xcode but without CLT”).
+  * Improve a couple of error messages: when getting mismatched versions of
+    cffi and its backend; and when calling functions which cannot be called 
with
+    libffi because an argument is a struct that is “too complicated” (and not
+    a struct pointer, which always works).
+  * Add support for some unusual compilers (non-msvc, non-gcc, non-icc, 
non-clang)
+  * Implemented the remaining cases for ffi.from_buffer. Now all
+    buffer/memoryview objects can be passed. The one remaining check is against
+    passing unicode strings in Python 2. (They support the buffer interface, 
but
+    that gives the raw bytes behind the UTF16/UCS4 storage, which is most of 
the
+    times not what you expect. In Python 3 this has been fixed and the unicode
+    strings don’t support the memoryview interface any more.)
+  * The C type _Bool or bool now converts to a Python boolean when reading,
+    instead of the content of the byte as an integer. The potential
+    incompatibility here is what occurs if the byte contains a value different
+    from 0 and 1. Previously, it would just return it; with this change, CFFI
+    raises an exception in this case. But this case means “undefined behavior”
+    in C; if you really have to interface with a library relying on this,
+    don’t use bool in the CFFI side. Also, it is still valid to use a byte
+    string as initializer for a bool[], but now it must only contain \x00 or
+    \x01. As an aside, ffi.string() no longer works on bool[] (but it never 
made
+    much sense, as this function stops at the first zero).
+  * ffi.buffer is now the name of cffi’s buffer type, and ffi.buffer() works
+    like before but is the constructor of that type.
+  * ffi.addressof(lib, "name") now works also in in-line mode, not only in
+    out-of-line mode. This is useful for taking the address of global 
variables.
+  * Issue #255: cdata objects of a primitive type (integers, floats, char) are
+    now compared and ordered by value. For example, <cdata 'int' 42> compares
+    equal to 42 and <cdata 'char' b'A'> compares equal to b'A'. Unlike C,
+    <cdata 'int' -1> 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.
+
+-------------------------------------------------------------------

Old:
----
  cffi-1.9.1.tar.gz

New:
----
  cffi-1.10.0.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-cffi.spec ++++++
--- /var/tmp/diff_new_pack.XuePNo/_old  2017-07-04 11:56:46.842993792 +0200
+++ /var/tmp/diff_new_pack.XuePNo/_new  2017-07-04 11:56:46.842993792 +0200
@@ -19,7 +19,7 @@
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 %define         modname cffi
 Name:           python-%{modname}
-Version:        1.9.1
+Version:        1.10.0
 Release:        0
 Summary:        Foreign Function Interface for Python calling C code
 License:        MIT

++++++ cffi-1.9.1.tar.gz -> cffi-1.10.0.tar.gz ++++++
++++ 3955 lines of diff (skipped)


Reply via email to