Skip to content

Move sage optimization backend framework (sage.numerical.backends) to separate Cython packages #28920

@mkoeppe

Description

@mkoeppe

This is a follow-up from #28175 (Move optional sage optimization backends (COIN, CPLEX, Gurobi) to separate Cython packages to remove OptionalExtension problems).

In fact, sage.numerical.backends depends on very little from Sage. We could move the entire backend machinery to a separate packages - for broadening the developer base and/or within the context of #26511.

Some notes regarding this:

See also:

CC: @isuruf @saraedum @kiwifb @dimpase @sagetrac-tmonteil @videlec

Component: numerical

Issue created by migration from https://trac.sagemath.org/ticket/28920

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions