From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: python3-nuitka
Date: Sat, 30 Dec 2023 01:24:38 +0100 [thread overview]
Message-ID: <20231230002438.zNZ6oRDpbMkP8oDs6OXBAD6Xyzl1x3VC_nbRSbclkLM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47982@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/47982#issuecomment-1872404161
Comment:
I definitely would not let such a special-interest package like this hold up the annual Python update, and agree that routinely breaking the package with updates would be a terrible experience that militates against packaging for Void.
As abby notes, the `python3.11` package exists **only** to a few packages that require Python to build (and vendor the packages they require for the process) and cannot build with the newer system version. Users are free to install that package and build virtual environments with it, but system packages that attempt to build modules for `python3.11` or link its libraries will not be allowed.
next prev parent reply other threads:[~2023-12-30 0:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 16:36 [ISSUE] Package request: michalszmidt
2023-12-29 19:16 ` Package request: python3-nuitka classabbyamp
2023-12-29 19:16 ` classabbyamp
2023-12-29 20:07 ` chrysos349
2023-12-29 22:36 ` michalszmidt
2023-12-29 22:49 ` classabbyamp
2023-12-29 22:51 ` classabbyamp
2023-12-29 22:51 ` classabbyamp
2023-12-30 0:24 ` ahesford [this message]
2023-12-30 0:24 ` ahesford
2023-12-30 1:07 ` michalszmidt
2023-12-31 15:54 ` ahesford
2023-12-31 15:54 ` [ISSUE] [CLOSED] " ahesford
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=20231230002438.zNZ6oRDpbMkP8oDs6OXBAD6Xyzl1x3VC_nbRSbclkLM@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).