From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-Cython: update to 3.0.1.
Date: Sun, 27 Aug 2023 16:12:27 +0200 [thread overview]
Message-ID: <20230827141227.-NksjVLMqWBUW7IqfYDyss8Wo0zBxjp6XYz6ZzuZHMI@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: 985 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/45086#issuecomment-1694679161
Comment:
> @tornaria I decided it wasn't worth trying to patch around all of these packages and added a new `python3-Cython0.29` which conflicts with `python3-Cython` and offers the "legacy" Cython 0.29.36. The legacy package can be a build-time dependency for the ~30 packages that have yet to support Cython 3. Only two packages have run-time dependencies on Cython: `urh` and `sagemath`. I have moved both the build-time and run-time dependencies of `urh` to `python3-Cython0.29` for now. How should I handle `sagemath`? We can do the same if you think that is the best course of action.
I think we have a way forward with sagemath (https://github.com/sagemath/sage/pull/36109 is almost done with review and https://github.com/sagemath/sage/pull/36110 is small). I think it might be possible to have sagemath running on cython 3 within the week.
next prev parent reply other threads:[~2023-08-27 14:12 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 [this message]
2023-08-28 15:23 ` 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
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=20230827141227.-NksjVLMqWBUW7IqfYDyss8Wo0zBxjp6XYz6ZzuZHMI@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).