From: Eddie Chapman <eddie@ehuk.net>
To: gentoo-dev@lists.gentoo.org, Benda Xu <heroxbd@gentoo.org>
Subject: Re: [gentoo-dev] Migrate away from python-2 or not
Date: Mon, 25 Nov 2019 07:41:25 +0000 [thread overview]
Message-ID: <ff7c4cec-9864-7da7-6a93-1b717c61fe74@ehuk.net> (raw)
In-Reply-To: <87a78l4gj2.fsf@robot.e.airelinux.org>
On 24/11/2019 12:15, Benda Xu wrote:
> Given the python-2 countdown deadline being 2020-01-01, a month away,
> shall we get rid of python-2?
> If the answer is no, to avoid holding back new versions having only
> python3, such as bug 671796 for dev-python/matplotlib bump, old versions
> with python_targets_python2_7 and new versions without should be
> co-installable into different SLOTs.
Rather than slots, perhaps a separate directory hierarchy containing
only python2 + deps (/opt/python2 ?) i.e. it's just a --prefix change
It's ugly I know but the advantage is the majority of installations with
python3 don't see any change and they'll have a clean python3 only /usr.
Anyone who wants/needs python2 will be happy to put up with the ugliness
and pull all the duplicate deps in (yes, have duplicate set of ebuilds
for python2 only deps - dev-python2/* - forked off and with the
understanding that no new features, this is a semi-temporary situation
until python2 can finally die properly). Also, I think it helps everyone
psychologically to have a very visible separation.
Not being a dev and with my lack of a deep understanding of python
there's probably an big reason this idea is a non-starter, so just
throwing it out there.
next prev parent reply other threads:[~2019-11-25 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 12:15 [gentoo-dev] Migrate away from python-2 or not Benda Xu
2019-11-24 13:31 ` Francesco Riosa
2019-11-24 18:13 ` Philip Webb
2019-11-25 7:41 ` Eddie Chapman [this message]
2019-11-25 8:39 ` Jaco Kroon
2019-11-29 13:49 ` Mathy Vanvoorden
2019-11-29 15:40 ` Haelwenn (lanodan) Monnier
2019-12-03 13:17 ` Benda Xu
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=ff7c4cec-9864-7da7-6a93-1b717c61fe74@ehuk.net \
--to=eddie@ehuk.net \
--cc=gentoo-dev@lists.gentoo.org \
--cc=heroxbd@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