baserev update by copy to link target

• Files Changed
• Browse Source

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

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- do not generate HTML documentation for packages that are indirect
  dependencies of Sphinx
  (see docs at https://cffi.readthedocs.org/ )

• Files Changed
• Browse Source

- split off -doc subpackage, to prevent build cycle with Sphinx

- separate cffi-doc subpackage to break build loop leading to Sphinx

• Files Changed
• Browse Source

singlespec + version update

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

Add upstream patch to actually fix problem with gcc >= 6; drop previous patch used to workaround issue.

• Files Changed
• Browse Source

- disable "negative left shift" warning in test suite to prevent
  failures with gcc6, until upstream fixes the undefined code
  in question (boo#981848, cffi-1.5.2-wnoerror.patch)

• Files Changed
• Browse Source

Update to v1.6.0; update fixes building against gcc >= 6

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 1.5.2
  * support for cffi-based embedding
  * more robustness for shutdown logic

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update to upstream release 1.4.2 (needed for new python-cryptography 1.2.1)

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to version 1.1.0 (fate#318838):

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to version 1.1.0
- add python-cffi-rpmlintrc: cffi specifically installs C headers in site-packages
- add new test dependency gcc-c++
- skip the tests on SLE11 since they fail on i586

• Files Changed
• Browse Source