From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sagemath: use cython 3
Date: Wed, 06 Sep 2023 16:50:19 +0200 [thread overview]
Message-ID: <20230906145019.DJ1GriRhbY_I_5AUB7Y1TGxSA8PSlYiy5njcON3ogAM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45887@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/45887#issuecomment-1708523022
Comment:
[I thought I already posted a response, but it seems lost to the ether.]
I understand that Sage built with Cython 0.29 is broken with Cython 3.0, but my point was that you can easily swap between installed Cython versions to test a locally built Sage with these patches.
The general policy for patches is that they should be limited to critical fixes in advance of an official release or correct an incompatibility introduced by our own packaging choices (*e.g.*, to support special aspects of our cross building). New features, even when merged upstream, should wait until an official release introduces them. This is particularly true here, where the patches to add support are more than 9k lines long.
next prev parent reply other threads:[~2023-09-06 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 22:32 [PR PATCH] " tornaria
2023-09-02 22:37 ` [PR PATCH] [Updated] " tornaria
2023-09-02 23:33 ` ahesford
2023-09-03 1:24 ` tornaria
2023-09-03 1:59 ` ahesford
2023-09-03 2:00 ` ahesford
2023-09-04 13:21 ` tornaria
2023-09-05 11:57 ` [PR PATCH] [Updated] " tornaria
2023-09-06 14:50 ` ahesford [this message]
2023-09-07 1:32 ` ahesford
2023-09-09 15:33 ` tornaria
2023-09-11 0:02 ` ahesford
2023-10-09 21:55 ` [PR PATCH] [Updated] " tornaria
2023-10-09 22:01 ` tornaria
2023-10-10 12:42 ` [PR PATCH] [Updated] " tornaria
2023-10-10 12:43 ` tornaria
2023-10-22 14:50 ` [PR PATCH] [Closed]: " tornaria
2023-10-22 14:50 ` tornaria
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230906145019.DJ1GriRhbY_I_5AUB7Y1TGxSA8PSlYiy5njcON3ogAM@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).