From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: python3-nuitka
Date: Fri, 29 Dec 2023 23:51:43 +0100 [thread overview]
Message-ID: <20231229225143.Kw5BcifZrzZs32THZjI_d2WgyqgyLjbxbiPy55A19WI@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: 735 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/47982#issuecomment-1872378408
Comment:
based on how long it appears to take them to be compatible with new python versions, this is probably not a good fit for void. void tries to bump its python very soon after the upstream release, so this would either hold everything up or be broken for months each year. neither seems like a good experience for users.
also, the way python works on void (and linux generally) does not need apps to be packed into a binary: there are system python modules that applications can rely on and (on void, at least) applications and libraries have python bytecode compilation at install-time.
next prev parent reply other threads:[~2023-12-29 22:51 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 [this message]
2023-12-30 0:24 ` ahesford
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=20231229225143.Kw5BcifZrzZs32THZjI_d2WgyqgyLjbxbiPy55A19WI@z \
--to=classabbyamp@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).