unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Does Guix provide security support for Python2? For how long?
Date: Fri, 15 Jan 2021 18:07:40 +0100	[thread overview]
Message-ID: <CAJ3okZ0Bp8KbWcbOVPUZ+kG2C=rEUUcdr6Z7uu_aWn2s+_2ZwQ@mail.gmail.com> (raw)
In-Reply-To: <87ft325gws.fsf@disroot.org>

Hi,

On Fri, 15 Jan 2021 at 17:02, Jorge P. de Morais Neto
<jorge+list@disroot.org> wrote:
>
> Hi.  I use Guix on a foreign distro---Debian buster (current stable).  I
> want to upgrade Debian to bullseye (current testing), but bullseye does
> not provide security support for Python 2.  I still use Python 2 for
> OfflineIMAP.  There is a Python 3 port of OfflineIMAP, but it was done
> very recently and I fear it is probably be buggy.  So I would like to
> install Guix Python 2 atop Debian bullseye just for OfflineIMAP.  Would
> that work fine?  Does Guix, unlike Debian bullseye, still provide
> security support for Python 2?  For how long?

As far as I know, Guix provides the security support that upstream releases.

Using the Guix time-machine, the code that works now should work
exactly the same in the future, even if Python 2 is removed in the
future Guix releases.  Does it make sense?


All the best,
simon


  reply	other threads:[~2021-01-15 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 16:00 Does Guix provide security support for Python2? For how long? Jorge P. de Morais Neto
2021-01-15 17:07 ` zimoun [this message]
2021-01-15 17:18   ` Jorge P. de Morais Neto
2021-01-15 18:17     ` dario
2021-01-15 18:28       ` Jorge P. de Morais Neto
2021-01-15 19:56     ` Leo Famulari
2021-01-15 20:06     ` zimoun

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='CAJ3okZ0Bp8KbWcbOVPUZ+kG2C=rEUUcdr6Z7uu_aWn2s+_2ZwQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@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.
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).