From: Lars-Dominik Braun <lars@6xq.net>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
zimon.toutoune@gmail.com,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
60240@debbugs.gnu.org, andreas@enge.fr, jgart <jgart@dismail.de>,
Marius Bakke <marius@gnu.org>,
john.kehayias@protonmail.com
Subject: [bug#60240] [PATCH v2] gnu: Add python-3.12 and python-next.
Date: Sun, 25 Feb 2024 15:08:20 +0100 [thread overview]
Message-ID: <ZdtJ1AU7ru7Vr2TU@noor.fritz.box> (raw)
In-Reply-To: <4832d706e706ced5aa8a52f1b63b1e676ea5fd3d.1708516654.git.tanguy@bioneland.org>
Hi,
> I created a brand new package definition for it, not inheriting from
> `python-2`. I actually copied/pasted the `python-2` package definition,
> removed what was specific to Python 2 and then copied over the things
> specific to Python 3 from the `python-3.10` package definition.
LGTM.
I believe the separate tk output does not give us any benefits regarding
closure size (any more?), because tcl and tk are both referenced from
`out`. Can we remove those references to reduce closure size again?
And I can also confirm test_asyncio runs out of memory on my machine
and test_threading never finishes. We should probably investigate both,
because they should not.
> - When I apply the patch I get whitespace errors, but I don’t know how
> those whitespace were introduced and how to get rid of them.
Line 641, as highlighted by `git show`.
> Btw, the patch targets the branch `python-team`.
I believe this change could target master, since it only adds python-3.12,
but does not cause any rebuilds using it.
Cheers,
Lars
next prev parent reply other threads:[~2024-02-25 14:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 15:32 [bug#60240] [PATCH] [WIP] gnu: Add python-3.11 Tanguy Le Carrour
2023-01-06 17:36 ` Simon Tournier
2023-01-09 15:59 ` Tanguy LE CARROUR
2023-03-12 23:35 ` [bug#60240] Python 3.10 in core-updates Andreas Enge
2024-02-19 21:27 ` John Kehayias via Guix-patches via
2024-02-20 14:18 ` Tanguy LE CARROUR
2024-02-21 12:13 ` [bug#60240] [PATCH v2] gnu: Add python-3.12 and python-next Tanguy Le Carrour
2024-02-21 18:36 ` Tanguy Le Carrour
2024-02-22 9:07 ` Tanguy LE CARROUR
2024-02-25 14:08 ` Lars-Dominik Braun [this message]
2024-02-26 8:25 ` Tanguy LE CARROUR
2024-03-02 9:59 ` Lars-Dominik Braun
2024-03-06 12:49 ` Tanguy LE CARROUR
2024-03-06 12:55 ` [bug#60240] [PATCH v3] " Tanguy Le Carrour
2024-03-07 18:45 ` [bug#60240] [PATCH v4] " Tanguy Le Carrour
2024-03-07 18:58 ` [bug#60240] [PATCH v5] " Tanguy Le Carrour
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=ZdtJ1AU7ru7Vr2TU@noor.fritz.box \
--to=lars@6xq.net \
--cc=60240@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=jgart@dismail.de \
--cc=john.kehayias@protonmail.com \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.org \
--cc=zimon.toutoune@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.