Accepting request 531217 from home:seanmarlow:branches:devel:languages:python

- 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.

OBS-URL: https://build.opensuse.org/request/show/531217
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-cffi?expand=0&rev=37

cffi-1.10.0.tar.gz

@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:b3b02911eb1f6ada203b0763ba924234629b51586f72a21faacc638269f4ced5
-size 418131

cffi-1.11.1.tar.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c40817cc0f71b5351eb0bdd0b585db4a285c2bcc03fbcb961b79bb8086b7576
+size 435135

python-cffi.changes

@@ -1,3 +1,69 @@
+-------------------------------------------------------------------
+Wed Oct  4 11:36:56 UTC 2017 - sean.marlow@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.marlow@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. 
+
 -------------------------------------------------------------------
 Thu Jun 29 16:03:46 UTC 2017 - tbechtold@suse.com
 

python-cffi.spec

@@ -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 @@ export CFLAGS="%{optflags}"
 %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,-)