Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency cffi to v1.17.1 #455

Closed

Conversation

red-hat-konflux[bot]
Copy link

@red-hat-konflux red-hat-konflux bot commented Nov 30, 2024

This PR contains the following updates:

Package Type Update Change
cffi (source, changelog) packages minor ==1.14.6 -> ==1.17.1
cffi (source, changelog) packages minor ==1.15.1 -> ==1.17.1

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

python-cffi/cffi (cffi)

v1.17.1

Compare Source

  • Fix failing distutils.msvc9compiler imports under Windows (#​118).
  • ffibuilder.emit_python_code() and ffibuiler.emit_c_code() accept file-like objects (#​115).
  • ffiplatform calls are bypassed by ffibuilder.emit_python_code() and ffibuilder.emit_c_code() (#​81).

Full Changelog: python-cffi/cffi@v1.17.0...v1.17.1

v1.17.0

Compare Source

  • Add support for Python 3.13.
    • Free-threaded CPython builds (i.e. python3.13t and the 3.13t ABI) are not currently supported.
  • 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.

Full Changelog: python-cffi/cffi@v1.16.0...v1.17.0

v1.16.0

Compare Source

  • Add support for Python 3.12. With the removal of distutils from Python 3.12, projects
    using CFFI features that depend on distutils at runtime must add a dependency on
    setuptools to function under Python 3.12+. CFFI does not declare a runtime setuptools
    requirement to avoid an unnecessary dependency for projects that do not require it.
  • Drop support for end-of-life Python versions (2.7, 3.6, 3.7).
  • Add support for PEP517 builds; setuptools is now a required build dependency.
  • Declare python_requires metadata for Python 3.8+. This allows unsupported Pythons
    to continue using previously released sdists and wheels.
  • Move project source under src/; a more standard layout that also enables CI to more easily
    catch packaging errors.

v1.15.1

Compare Source

(retroactive GitHub release for current stable version 1.15.1)

  • If you call ffi.embedding_api() but don't write any extern "Python" function there, then the resulting C code would fail an assert. Fixed.
  • Updated Windows/arm64 embedded libffi static lib to v3.4.2, and scripted to ease future updates (thanks Niyas Sait!)

Full Changelog: python-cffi/cffi@v1.15.0...v1.15.1

v1.15.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 5am on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@openshift-ci openshift-ci bot requested review from dibryant and harshad16 November 30, 2024 16:23
Copy link

openshift-ci bot commented Nov 30, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign harshad16 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

openshift-ci bot commented Nov 30, 2024

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a red-hat-data-services member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link
Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (==1.17.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/konflux-poc/cffi-1.x branch December 20, 2024 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant