From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-Cython: update to 3.0.1.
Date: Sun, 03 Sep 2023 00:32:57 +0200 [thread overview]
Message-ID: <20230902223257.A0X_UERepwlDord69Z5FNL8AZ3O3NVoFyqwr4Tktf3A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45086@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/45086#issuecomment-1703955469
Comment:
> With `python3-pplpy` built with `python3-Cython0.29` (which is its current state in the repository), all `sagemath` tests in the `--long` suite pass (with the exception of some new warnings emitted by Pythran), so this is good to go; merged as [cb4c843](https://github.com/void-linux/void-packages/commit/cb4c843f1feb13347fb472aa71d18f450a0a5413).
https://github.com/sagemath/sage/pull/36109 was merged a few hours after you merged this, and that is the only "long" part of the move to cython 3.
The actual patch needed on top of that to be able to use cython 3 is just 6 lines (plus 19 lines in doctests due to some changed strings). See #45887 for details.
prev parent reply other threads:[~2023-09-02 22:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 17:20 [PR PATCH] python3-Cython: update to 3.0.0 ahesford
2023-07-17 19:00 ` tornaria
2023-07-17 19:04 ` ahesford
2023-07-17 19:19 ` [PR PATCH] [Updated] " ahesford
2023-07-17 20:14 ` ahesford
2023-07-18 9:27 ` icp1994
2023-07-18 11:11 ` ahesford
2023-07-18 17:43 ` [PR PATCH] [Updated] " ahesford
2023-07-18 17:45 ` ahesford
2023-07-19 2:35 ` ahesford
2023-07-20 23:33 ` tornaria
2023-07-21 1:40 ` [PR PATCH] [Updated] " ahesford
2023-07-21 2:46 ` [PR REVIEW] " tornaria
2023-07-21 12:33 ` [PR PATCH] [Updated] " ahesford
2023-07-31 20:29 ` ahesford
2023-08-26 3:13 ` ahesford
2023-08-26 3:24 ` ahesford
2023-08-26 17:31 ` [PR PATCH] [Updated] python3-Cython: update to 3.0.1 ahesford
2023-08-26 20:04 ` ahesford
2023-08-26 20:04 ` [PR PATCH] [Updated] " ahesford
2023-08-26 20:43 ` ahesford
2023-08-27 14:12 ` tornaria
2023-08-28 15:23 ` [PR PATCH] [Updated] " ahesford
2023-08-28 15:26 ` ahesford
2023-08-31 1:02 ` ahesford
2023-08-31 1:15 ` ahesford
2023-08-31 14:01 ` ahesford
2023-09-01 14:36 ` ahesford
2023-09-01 15:13 ` ahesford
2023-09-01 17:32 ` [PR PATCH] [Closed]: " ahesford
2023-09-01 17:34 ` ahesford
2023-09-02 22:32 ` tornaria [this message]
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=20230902223257.A0X_UERepwlDord69Z5FNL8AZ3O3NVoFyqwr4Tktf3A@z \
--to=tornaria@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).