unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: guix-devel@gnu.org
Subject: the upcoming Great Python2 Purge™
Date: Wed, 26 Dec 2018 11:38:12 +0200	[thread overview]
Message-ID: <20181226093812.GR2581@macbook41> (raw)

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

We're now about a year out from the official EOL for python2 (Jan 1,
2020). So far we've been not adding python2 variants of packages that
are new unless they're actually needed for something. Do we want to
start removing python2 packages when updating other packages if they are
leaf packages?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-12-26  9:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26  9:38 Efraim Flashner [this message]
2018-12-26 12:30 ` the upcoming Great Python2 Purge™ Marius Bakke
2018-12-26 13:33   ` add DEPRECATION grace period: " Pjotr Prins
2018-12-27  4:47     ` Leo Famulari
2018-12-27 15:52       ` Alex Vong
2018-12-27  4:50   ` Leo Famulari
2018-12-26 19:47 ` Konrad Hinsen
2018-12-27  4:38 ` Leo Famulari
2018-12-27 14:49   ` Brett Gilio
2019-02-18  9:56 ` Efraim Flashner
2019-02-18 10:16   ` Konrad Hinsen
2019-02-18 10:29     ` Ricardo Wurmus
2019-02-18 11:02       ` Konrad Hinsen
2019-02-18 11:07         ` Ricardo Wurmus
2019-02-18 14:42           ` zimoun
2019-02-18 16:30           ` Konrad Hinsen
2019-02-18 16:54             ` the upcoming Great Python2 Purge�?� ng0
2019-02-18 19:27             ` the upcoming Great Python2 Purge™ zimoun
2019-02-18 18:38   ` Brett Gilio
2019-02-18 21:39   ` Björn Höfling

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181226093812.GR2581@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).