From: David Seifert <soap@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade
Date: Sun, 12 Jan 2020 23:46:19 +0100 [thread overview]
Message-ID: <e64dfb6902b302f8be89f763b4a87ea165e4d5ff.camel@gentoo.org> (raw)
In-Reply-To: <390fadf1-4a72-24b8-049e-1ab5925590da@gentoo.org>
On Sun, 2020-01-12 at 17:43 -0500, Joshua Kinard wrote:
> On 1/12/2020 17:32, Andreas Sturmlechner wrote:
> > On Sonntag, 12. Januar 2020 23:07:24 CET Joshua Kinard wrote:
> > > It might be worthwhile to treat the removal of Python-2.7 from
> > > the tree in
> > > the same manner as an EAPI deprecation and removal, given how
> > > ingrained it
> > > is due to its longevity. That will minimize the whiplash-effect
> > > of emerge
> > > complaining about slot conflicts and dependency conflicts. Like
> > > I just ran
> > > into w/ setuptools-45.0.0.0's release.
> >
> > So, no packaging of >=setuptools-45.0.0 until the end of 2020? Do
> > you want to
> > freeze all python libs that upstreams are dropping py27 support
> > from?
> >
>
> Not saying not to package it. Right now, the issue seems to be it
> causes
> dependency conflicts in emerge's depgraph parsing when PYTHON_TARGETS
> includes python2_7 support. Remove that and stick with python3_*
> only, then
> other packages that need python2_7 will whine.
>
> Did setuptools-45.0.0 remove all python2 support? I looked at the
> commit
> log, and it's only the title that any meaningful hint that it may
> have,
> "dev-python/setuptools: Bump to 45.0.0 (py3 only)". If it did, then
> that
> change is the right change, but anyone with a userland that has a mix
> of
> python2 and python3 is going to have difficulty getting that update
> to merge
> in, so I really can't go higher than setuptools-44.0.0 for the time
> being.
>
https://setuptools.readthedocs.io/en/latest/history.html#v45-0-0
next prev parent reply other threads:[~2020-01-12 22:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:42 [gentoo-dev] unsanctioned python 2.7 crusade Jason A. Donenfeld
2019-12-05 13:55 ` Rich Freeman
2019-12-05 13:59 ` Jason A. Donenfeld
2019-12-05 14:24 ` Rich Freeman
2019-12-05 14:34 ` William Breathitt Gray
2019-12-05 14:40 ` Aaron Bauman
2019-12-06 6:53 ` Kent Fredric
2020-01-12 22:07 ` Joshua Kinard
2020-01-12 22:17 ` David Seifert
2020-01-12 22:29 ` Joshua Kinard
2020-01-12 22:32 ` Andreas Sturmlechner
2020-01-12 22:43 ` Joshua Kinard
2020-01-12 22:46 ` David Seifert [this message]
2020-01-12 22:55 ` Joshua Kinard
2020-01-12 23:17 ` David Seifert
2020-01-13 0:21 ` William Hubbs
2020-01-13 0:44 ` Joshua Kinard
2020-01-13 7:22 ` Andreas Sturmlechner
2020-01-13 6:52 ` Michał Górny
2020-01-14 6:45 ` Joshua Kinard
2019-12-05 20:31 ` David Seifert
2019-12-05 20:56 ` Thomas Deutschmann
2019-12-05 22:23 ` David Seifert
2019-12-05 22:41 ` Rich Freeman
2019-12-06 8:11 ` Mart Raudsepp
2019-12-06 10:48 ` David Seifert
2019-12-06 13:06 ` Thomas Deutschmann
2019-12-06 13:52 ` Rich Freeman
2019-12-06 15:48 ` Mike Gilbert
2019-12-06 16:12 ` Thomas Deutschmann
2019-12-06 16:44 ` Mike Gilbert
2019-12-06 19:47 ` Thomas Deutschmann
2019-12-06 20:10 ` Andreas Sturmlechner
2019-12-06 20:28 ` Thomas Deutschmann
2019-12-08 10:28 ` Alexis Ballier
2019-12-06 20:30 ` Michael 'veremitz' Everitt
2019-12-07 8:04 ` Kent Fredric
2019-12-06 16:35 ` Mart Raudsepp
2019-12-06 16:43 ` Thomas Deutschmann
2019-12-05 14:36 ` Aaron Bauman
2019-12-05 16:03 ` Andreas K. Huettel
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=e64dfb6902b302f8be89f763b4a87ea165e4d5ff.camel@gentoo.org \
--to=soap@gentoo.org \
--cc=gentoo-dev@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