From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Problem with packages losing python2 compatibility
Date: Mon, 10 Dec 2018 11:59:28 -0500 [thread overview]
Message-ID: <26ae5bda-a8d5-0937-7165-6e7cd4c59105@gentoo.org> (raw)
In-Reply-To: <1544458022.19874.17.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1249 bytes --]
On 2018-12-10 11:07 a.m., Michał Górny wrote:
> What can we do to solve it?
> ===========================
>
> a) Do nothing and hope upstreams solve it at some point. I don't think
> this is acceptable because Portage's slowdown is going to be
> significant.
>
> b) Start dropping py2 from packages. Sadly, this is hard because we're
> talking about huge reverse dependency graph, and I'm pretty sure some of
> our users need those packages w/ py2 support.
>
> c) Slot IPython? That's probably the least intrusive option, though
> ugly as hell, and I'm not sure if it's not going to impact dep
> calculation severely anyway. We'd have a :5 slot that supports py2
> only, and :0 slot that supports py3 only. Dependencies will be tricky,
> life's going to be hard but maybe things will work.
>
> Any other options?
This'll be uglier for maintainers but cleaner for the repo -- what
about a single IPython "package" that installs :5 for py2 and :0 for
py3 ? Since python multi-builds anyways it shouldn't be too difficult
to have it install from separate distfiles. Versioning would be a
royal pain, likely some sort of combination of versions into a
snapshot version number of sorts would need to be done...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2018-12-10 16:59 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
2018-12-10 16:59 ` Ian Stakenvicius [this message]
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=26ae5bda-a8d5-0937-7165-6e7cd4c59105@gentoo.org \
--to=axs@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