Hello community,
here is the log from the commit of package python-cffi for openSUSE:Factory
checked in at 2017-10-10 11:34:16
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-cffi (Old)
and /work/SRC/openSUSE:Factory/.python-cffi.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-cffi"
Tue Oct 10 11:34:16 2017 rev:17 rq:531228 version:1.11.1
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-cffi/python-cffi.changes 2017-07-04
11:56:45.787142379 +0200
+++ /work/SRC/openSUSE:Factory/.python-cffi.new/python-cffi.changes
2017-10-10 11:34:21.622188188 +0200
@@ -1,0 +2,66 @@
+Wed Oct 4 11:36:56 UTC 2017 - sean.mar...@suse.com
+
+- Update pytest in spec to add c directory tests in addition to
+ testing directory.
+- Omit test_init_once_multithread tests as they rely on multiple
+ threads finishing in a given time. Returns sporadic pass/fail
+ within build.
+- Update to 1.11.1:
+ * Fix tests, remove deprecated C API usage
+ * Fix (hack) for 3.6.0/3.6.1/3.6.2 giving incompatible binary
+ extensions (cpython issue #29943)
+ * Fix for 3.7.0a1+
+
+-------------------------------------------------------------------
+Thu Sep 28 15:00:46 UTC 2017 - sean.mar...@suse.com
+
+- Update to 1.11.0:
+ * Support the modern standard types char16_t and char32_t. These
+ work like wchar_t: they represent one unicode character, or when
+ used as charN_t * or charN_t[] they represent a unicode string.
+ The difference with wchar_t is that they have a known, fixed
+ size. They should work at all places that used to work with
+ wchar_t (please report an issue if I missed something). Note
+ that with set_source(), you need to make sure that these types
+ are actually defined by the C source you provide (if used in
+ cdef()).
+ * Support the C99 types float _Complex and double _Complex. Note
+ that libffi doesn’t support them, which means that in the ABI
+ mode you still cannot call C functions that take complex
+ numbers directly as arguments or return type.
+ * Fixed a rare race condition when creating multiple FFI instances
+ from multiple threads. (Note that you aren’t meant to create
+ many FFI instances: in inline mode, you should write
+ ffi = cffi.FFI() at module level just after import cffi; and in
+ out-of-line mode you don’t instantiate FFI explicitly at all.)
+ * Windows: using callbacks can be messy because the CFFI internal
+ error messages show up to stderr—but stderr goes nowhere in many
+ applications. This makes it particularly hard to get started
+ with the embedding mode. (Once you get started, you can at least
+ use @ffi.def_extern(onerror=...) and send the error logs where
+ it makes sense for your application, or record them in log
+ files, and so on.) So what is new in CFFI is that now, on
+ Windows CFFI will try to open a non-modal MessageBox (in addition
+ to sending raw messages to stderr). The MessageBox is only
+ visible if the process stays alive: typically, console
+ applications that crash close immediately, but that is also the
+ situation where stderr should be visible anyway.
+ * Progress on support for callbacks in NetBSD.
+ * Functions returning booleans would in some case still return 0
+ or 1 instead of False or True. Fixed.
+ * ffi.gc() now takes an optional third parameter, which gives an
+ estimate of the size (in bytes) of the object. So far, this is
+ only used by PyPy, to make the next GC occur more quickly
+ (issue #320). In the future, this might have an effect on
+ CPython too (provided the CPython issue 31105 is addressed).
+ * Add a note to the documentation: the ABI mode gives function
+ objects that are slower to call than the API mode does. For
+ some reason it is often thought to be faster. It is not!
+- Update to 1.10.1:
+ * Fixed the line numbers reported in case of cdef() errors. Also,
+ I just noticed, but pycparser always supported the preprocessor
+ directive # 42 "foo.h" to mean “from the next line, we’re in
+ file foo.h starting from line 42”, which it puts in the error
+ messages.
+
+-------------------------------------------------------------------
Old:
----
cffi-1.10.0.tar.gz
New:
----
cffi-1.11.1.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-cffi.spec ++++++
--- /var/tmp/diff_new_pack.anAgXT/_old 2017-10-10 11:34:22.622144302 +0200
+++ /var/tmp/diff_new_pack.anAgXT/_new 2017-10-10 11:34:22.626144126 +0200
@@ -19,7 +19,7 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
%define modname cffi
Name: python-%{modname}
-Version: 1.10.0
+Version: 1.11.1
Release: 0
Summary: Foreign Function Interface for Python calling C code
License: MIT
@@ -55,7 +55,7 @@
%python_install
%check
-%python_expand PYTHONPATH=%{buildroot}%{$python_sitearch}
py.test-%$python_bin_suffix
+%python_expand PYTHONPATH=%{buildroot}%{$python_sitearch}
py.test-%$python_bin_suffix -k "not test_init_once_multithread" c/ testing/
%files %{python_files}
%defattr(-,root,root,-)
++++++ cffi-1.10.0.tar.gz -> cffi-1.11.1.tar.gz ++++++
++++ 5209 lines of diff (skipped)
