diff options
| author | Tim Orling <tim.orling@konsulko.com> | 2024-08-12 21:18:52 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-08-15 14:51:55 +0100 |
| commit | 36d7994e7e3925b7c031837e84b03309a4634cdb (patch) | |
| tree | 2b6aaa0aea6ad0ebcca257212517c9ae009556a4 /meta/recipes-devtools/python/python3/crosspythonpath.patch | |
| parent | bb6241fcdc62b7af0f87364a5e8808f94a21ab5b (diff) | |
| download | poky-36d7994e7e3925b7c031837e84b03309a4634cdb.tar.gz | |
python3-cffi: upgrade 1.16.0 -> 1.17.0
https://github.com/python-cffi/cffi/compare/v1.17.0...v1.16.0
https://cffi.readthedocs.io/en/latest/whatsnew.html#v1-17
v1.17
* 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.
(From OE-Core rev: 375e59bfb4d610f89dd04c93f912d5847a5fac4f)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3/crosspythonpath.patch')
0 files changed, 0 insertions, 0 deletions
