python/python-cffi
SHA256
15
0
Fork 0
forked from pool/python-cffi
Code Pull Requests Activity

- update to 1.17.0:

Browse Source 
* Add support for Python 3.13.
  * In API mode, when you get a function from a C library by writing
    `fn = lib.myfunc`, you get an object of a special type for
    performance reasons, instead of a `<cdata 'C-function-type'>`.
    Before version 1.17 you could only call such objects.
    You could write `ffi.addressof(lib, "myfunc")` in order to get
    a real `<cdata>` object, based on the idea that in these cases
    in C you'd usually write `&myfunc` instead of `myfunc`.  In
    version 1.17, the special object `lib.myfunc` can now be passed
    in many places where CFFI expects
    a regular `<cdata>` object.  For example, you can now pass
    it as a callback to a C function call, or write it inside a C
    structure field of the correct pointer-to-function type, or use
    `ffi.cast()` or `ffi.typeof()` on it.
- drop py313-compat.patch, py313-use-format-unraisable.patch,
  py313-use-hashpointer.patch (upstream)

OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-cffi?expand=0&rev=99
This commit is contained in:
Dirk Mueller
2024-08-31 12:55:13 +00:00
committed by Git OBS Bridge
parent 66022bf2e9
commit b61b47e37f
7 changed files with 25 additions and 371 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
python-cffi.changes
View File

@@ -1,3 +1,24 @@
-------------------------------------------------------------------
Sat Aug 31 12:39:52 UTC 2024 - Dirk Müller <dmueller@suse.com>
- update to 1.17.0:
* Add support for Python 3.13.
* In API mode, when you get a function from a C library by writing
`fn = lib.myfunc`, you get an object of a special type for
performance reasons, instead of a `<cdata 'C-function-type'>`.
Before version 1.17 you could only call such objects.
You could write `ffi.addressof(lib, "myfunc")` in order to get
a real `<cdata>` object, based on the idea that in these cases
in C you'd usually write `&myfunc` instead of `myfunc`. In
version 1.17, the special object `lib.myfunc` can now be passed
in many places where CFFI expects
a regular `<cdata>` object. For example, you can now pass
it as a callback to a C function call, or write it inside a C
structure field of the correct pointer-to-function type, or use
`ffi.cast()` or `ffi.typeof()` on it.
- drop py313-compat.patch, py313-use-format-unraisable.patch,
py313-use-hashpointer.patch (upstream)
-------------------------------------------------------------------
Sun Jun 30 21:26:53 UTC 2024 - Dirk Müller <dmueller@suse.com>