Skip to content

Drop PIP_CONSTRAINT info when PETSc next releases #5380

Description

@connorjward

In #5376 we set a PIP_CONSTRAINT file to manage a Cython breakage in petsc4py. PETSc have now fixed this so we just need to wait for their next patch release before we can remove the instructions.

Activity

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

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions