Upgrade cvxopt to 1.2.7 for python 3.10

[mkoeppe]

cvxopt 1.2.7 has merged
cvxopt/cvxopt#190

Upstream: Fixed upstream, in a later stable release.

CC: @dimpase @orlitzky

Component: packages: standard

Author: Matthias Koeppe

Branch/Commit: 380b63a

Reviewer: Dima Pasechnik

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

[mkoeppe]

Branch: u/mkoeppe/patch_cvxopt_for_python_3_10

[mkoeppe]

New commits:

9966a17

build/pkgs/cvxopt/patches: Add https://github.com/cvxopt/cvxopt/pull/190

[mkoeppe]

Commit: 9966a17

[orlitzky]

comment:4

I think we should wait and give upstream some time to respond, at least until python-3.10 is released and available in mainstream distros. Otherwise we will end up supporting python-3.10 only via patches and rejecting system packages on distros that don't have the unofficial patches.

[mkoeppe]

comment:5

Note the pull request is from early spring this year...

[mkoeppe]

comment:6

Replying to @orlitzky:

Otherwise we will end up supporting python-3.10 only via patches and rejecting system packages on distros that don't have the unofficial patches.

We don't use system packages for any Python packages, so this is a non-issue

[orlitzky]

comment:7

Replying to @mkoeppe:

We don't use system packages for any Python packages

.. yet. One of the obstacles standing in our way (although not a problem unique to python packages) is custom patching.

If we have to patch, we can patch; it just seems a little early for the nuclear option.

[mkoeppe]

comment:8

Replying to @orlitzky:

Replying to @mkoeppe:

We don't use system packages for any Python packages

.. yet.

Frankly it's pretty unrealistic for the Sage distribution to support it any time soon. I've sketched the best approach in #29023 and it's pretty complicated.

One of the obstacles standing in our way (although not a problem unique to python packages) is custom patching.

I agree (see #31543) that the Sage library should not depend on custom patched Python packages.

But this cannot stop us to fix the Sage distribution so that it does not run into build problems. Note in particular that this build problem (of a standard package!) stops developers from actually testing Python 3.10 and therefore blocks necessary progress in our library.

If it helps, think of the Sage distribution as a reference environment for developers.

If we have to patch, we can patch; it just seems a little early for the nuclear option.

That's a little dramatic. To stay within your metaphor, we already have dozens of nuclear plants running -- adding another one technically is to take the "nuclear option" but lacks the drama that this turn of phrase is meant to invoke.

[mkoeppe]

Reviewer: https://github.com/mkoeppe/sage/actions/runs/1242854091, https://github.com/mkoeppe/sage/actions/runs/1242854090

[dimpase]

comment:10

Replying to @mkoeppe:

Note the pull request is from early spring this year...

cvxopt's upstream is very, very slow at times.

[mkoeppe]

Upstream: Fixed upstream, but not in a stable release.

[orlitzky]

comment:12

the pull request may be resolved but the vicious attack on my metaphor can't be undone

[mkoeppe]

comment:13

It was a conventional attack on your nuclear metaphor though

[mkoeppe]

Changed upstream from Fixed upstream, but not in a stable release. to Fixed upstream, in a later stable release.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

380b63a

build/pkgs/cvxopt: Update to 1.2.7 for Python 3.10 compatibility

[sagetrac-git]

Changed commit from 9966a17 to 380b63a

[mkoeppe]

Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/1242854091, https://github.com/mkoeppe/sage/actions/runs/1242854090 to none

[dimpase]

Reviewer: Dima Pasechnik

[dimpase]

comment:17

OK

[vbraun]

Changed branch from u/mkoeppe/patch_cvxopt_for_python_3_10 to 380b63a