Skip to content

Unpin cffi from version < 1.17 #3340

Description

@schnellerhase

The release of cffi version v1.17.0 broke the red hat CI pipeline.

An explicit downgrade as hot fix was introduced in #3339. This should be reverted, to using the latest version of cffi in its runs, to fix this issue.

Interestingly this seems to be a platform dependent problem as the other CI runs did not reproduce the behavior.

Activity

  1. changed the title [-]Make redhat pipeline compatbile with cffi version 1.17.0[/-] [+]Unpin cffi from version 1.16.0[/+] on Sep 24, 2024
  2. garth-wells commented on Oct 2, 2024

    @garth-wells
    Member

    Unpin once python-cffi/cffi#111 is in cffi release.

    See also python-cffi/cffi#127.

  3. added this to the 0.10.0 milestone on Oct 2, 2024
  4. changed the title [-]Unpin cffi from version 1.16.0[/-] [+]Unpin cffi from version < 1.17[/+] on Oct 15, 2024
  5. francesco-ballarin commented on Feb 13, 2025

    @francesco-ballarin
    Member

    Just a heads up that on my Debian testing system cffi<1.17 failed to compile from source with python 3.13, while cffi==1.17 works fine (and is already packaged). The pin should ideally be gone before our next release if at all possible (meaning, if cffi does have a new release in the meantime).

  6. garth-wells commented on Feb 13, 2025

    @garth-wells
    Member

    We should unpin cffi now, and raise an exception if a user tries to use it with a complex type (and advise them to rollback cffi).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions