From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: Sharlatan Hellseher <sharlatanus@gmail.com>,
Simon Tournier <zimon.toutoune@gmail.com>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Lars-Dominik Braun <lars@6xq.net>,
60240@debbugs.gnu.org, Andreas Enge <andreas@enge.fr>,
jgart <jgart@dismail.de>, Marius Bakke <marius@gnu.org>
Subject: [bug#60240] Python 3.10 in core-updates
Date: Mon, 19 Feb 2024 21:27:48 +0000 [thread overview]
Message-ID: <875xyk9mbc.fsf@protonmail.com> (raw)
In-Reply-To: <20221221153230.27764-1-tanguy@bioneland.org>
Hello,
I was curious about python 3.11 and dug up this issue so I thought I
would check in (CC'ing python-team and original people on the thread).
A link for a refresher: <https://issues.guix.gnu.org/60240>
On Mon, Mar 13, 2023 at 12:35 AM, Andreas Enge wrote:
> Hello Tanguy,
>
> core-updates has Python 3.10.7, so you may wish to base your work on this
> branch and submit it once the branch has been merged.
>
Yes, we have and default to python-3.10 in master but it would be great
to have python-3.11. We could add this as "python-next" and start seeing
what packages can build with 3.11 before deciding if/when to switch
over.
Tanguy: have you tried your patch recently at all? Can we base it off of
3.10 and have a working 3.11 from what you started?
Thanks!
John
> There python@3 still inherits from python2@2. But since it overwrites all
> interesting fields, I think it would make sense to write a package definition
> "from scratch" by copying fields such as home-page etc.
>
> Good luck with packaging!
>
> Andreas
next prev parent reply other threads:[~2024-02-19 21:29 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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
2024-11-08 8:00 ` bug#60240: " Lars-Dominik Braun
2024-11-08 10:08 ` [bug#60240] " 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=875xyk9mbc.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=60240@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=jgart@dismail.de \
--cc=john.kehayias@protonmail.com \
--cc=lars@6xq.net \
--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.