From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] For next council meeting: moving Portage to python3.6+
Date: Sat, 24 Feb 2018 20:06:17 +0000 [thread overview]
Message-ID: <84e11bd8-34d9-6ac6-af0f-960b48a84c10@iee.org> (raw)
In-Reply-To: <CAPDOV49JWHjQr_ZXw5qE7qWh=coWt0TnPvSm=+4CP-CwkiAaEQ@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1260 bytes --]
On 24/02/18 19:57, Daniel Robbins wrote:
> On Sat, Feb 24, 2018 at 12:50 PM, M. J. Everitt <m.j.everitt@iee.org
> <mailto:m.j.everitt@iee.org>> wrote:
>
> So, all that remains is who's gonna do the work - both on the
> stabilisation of python3.6 as a dev-lang package, and all the
> associated (thousands?) of dev-python packages?
> You may have brought Zac on board on the portage side of things,
> but what about the rest?
>
>
> Good question, here is the answer.
>
> Standardizing on 3.6+ support for Portage does not require Gentoo to
> get rid of 2.7.
>
> The thousands? of ebuilds that need 2.7 continue to need 2.7.
>
> Dropping support for 2.7 also doesn't require ANY code changes to
> Portage. It is a strategic decision to not *continue* to maintain 2./7
> support in the future if *it becomes an annoyance or limitation* for
> us to do so. In some areas, we are finding that it is.
>
> Also, on a side-note, I have been personally helping Gentoo with the
> effort of removing pycrypto dependencies from Python modules.
>
> -Daniel
>
>
It would seem I've overlooked the fact that python3.6 is actually pretty
well supported in Gentoo .. my apologies to the Python team for failing
to spot this.
[-- Attachment #1.1.2: Type: text/html, Size: 2880 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-02-24 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 2:58 [gentoo-project] For next council meeting: moving Portage to python3.6+ Daniel Robbins
2018-02-24 4:42 ` [gentoo-project] " Benda Xu
2018-02-24 8:57 ` [gentoo-project] " Michał Górny
2018-02-24 17:55 ` R0b0t1
2018-02-24 19:45 ` Daniel Robbins
2018-02-24 19:50 ` M. J. Everitt
2018-02-24 19:57 ` Daniel Robbins
2018-02-24 20:06 ` M. J. Everitt [this message]
2018-02-24 20:44 ` R0b0t1
2018-04-18 15:58 ` Zac Medico
2018-04-25 6:56 ` Michał Górny
2018-04-25 9:42 ` Zac Medico
2018-04-25 9:29 ` nado
2018-04-25 11:50 ` Raymond Jennings
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=84e11bd8-34d9-6ac6-af0f-960b48a84c10@iee.org \
--to=m.j.everitt@iee.org \
--cc=gentoo-project@lists.gentoo.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