all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: 60240@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: [bug#60240] [PATCH] [WIP] gnu: Add python-3.11.
Date: Mon, 09 Jan 2023 16:59:55 +0100	[thread overview]
Message-ID: <167327999599.20007.5827702388142340079@localhost> (raw)
In-Reply-To: <877cxzh8ez.fsf@gmail.com>

Hi Simon,

Believe it or not, I sent the patch before I went on vacation and… I kind
of forgot about it! 😅


Quoting Simon Tournier (2023-01-06 18:36:36)
> On Wed, 21 Dec 2022 at 16:32, Tanguy Le Carrour <tanguy@bioneland.org> wrote:
> 
> > This leads me to my first question: wouldn't it be better to write a "fresh"
> > package definition not inheriting from `python-2` (deprecated since 2020) and
> > `python-3.9` (soon to be replaced)?
> 
> Yes, it would be nice to have Python 3 as the package definition.  And
> maybe Python 2 as inheriting from Python 3. :-)

I'm not saying that we should do the same but… Debian is dropping
support for Python 2 in the next release [1].

[1]: https://wiki.debian.org/Python/FAQ#Python_2_support


> > Another question would be: should I first write a package definition
> > for `python-3.10` so we have it in the history and one could use the
> > time machine to install it?
> 
> Well, it appears to me fine to jump from 3.9 to 3.11 dropping 3.10.

You know what they say, who can do more can do less! 😁

Regards,

-- 
Tanguy




  reply	other threads:[~2023-01-09 16:01 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 [this message]
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
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=167327999599.20007.5827702388142340079@localhost \
    --to=tanguy@bioneland.org \
    --cc=60240@debbugs.gnu.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.