From: grozin@gentoo.org
To: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] Problem with packages losing python2 compatibility
Date: Mon, 10 Dec 2018 23:44:35 +0700 (+07) [thread overview]
Message-ID: <alpine.LRH.2.21.1812102328420.22146@star.inp.nsk.su> (raw)
In-Reply-To: <1544458022.19874.17.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Mon, 10 Dec 2018, Michał Górny wrote:
> Now, IPython is now split upstream into two branches: 5 and 6. The old
> branch 5 supports py2+py3 which is good. The new branch 6 supports py3
> only. This means that any IPython revdep that requires py2 needs to
> force the old branch.
The current version is 7.2 already. The branch 7 is py3 only, of course.
> Unless someone has a better idea, I think a combined b+c approach might
> be the way to go. That is:
>
> 1. slot IPython as described above.
>
> 2. update py2+py3 revdeps to use proper cond-dep for slotted version.
>
> 3. slowly drop py2 from revdeps whenever possible.
Seems reasonable. I'm eager to try ipython-7.x.
Another similar case is matplotlib. The branch 3 (not yet in our tree) is
py3 only. Probably, other major projects will become py3-only soon.
For example, I use py3 whenever I can. But I use a few py2-only
packages, such as dev-util/diffuse (a very nice gui diff/merge tool, based
on pygtk, the latest release in 2014). I hope py2.7 and simple py2-only
packages without numerous deps (like diffuse) will live in the tree for a
long enough time.
Andrey
next prev parent reply other threads:[~2018-12-10 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 16:07 [gentoo-python] Problem with packages losing python2 compatibility Michał Górny
2018-12-10 16:44 ` grozin [this message]
2018-12-10 16:59 ` Ian Stakenvicius
2018-12-10 19:41 ` Michał Górny
2018-12-11 13:49 ` Virgil Dupras
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=alpine.LRH.2.21.1812102328420.22146@star.inp.nsk.su \
--to=grozin@gentoo.org \
--cc=gentoo-python@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