| 1 |
On Sun, 2020-01-12 at 17:43 -0500, Joshua Kinard wrote: |
| 2 |
> On 1/12/2020 17:32, Andreas Sturmlechner wrote: |
| 3 |
> > On Sonntag, 12. Januar 2020 23:07:24 CET Joshua Kinard wrote: |
| 4 |
> > > It might be worthwhile to treat the removal of Python-2.7 from |
| 5 |
> > > the tree in |
| 6 |
> > > the same manner as an EAPI deprecation and removal, given how |
| 7 |
> > > ingrained it |
| 8 |
> > > is due to its longevity. That will minimize the whiplash-effect |
| 9 |
> > > of emerge |
| 10 |
> > > complaining about slot conflicts and dependency conflicts. Like |
| 11 |
> > > I just ran |
| 12 |
> > > into w/ setuptools-45.0.0.0's release. |
| 13 |
> > |
| 14 |
> > So, no packaging of >=setuptools-45.0.0 until the end of 2020? Do |
| 15 |
> > you want to |
| 16 |
> > freeze all python libs that upstreams are dropping py27 support |
| 17 |
> > from? |
| 18 |
> > |
| 19 |
> |
| 20 |
> Not saying not to package it. Right now, the issue seems to be it |
| 21 |
> causes |
| 22 |
> dependency conflicts in emerge's depgraph parsing when PYTHON_TARGETS |
| 23 |
> includes python2_7 support. Remove that and stick with python3_* |
| 24 |
> only, then |
| 25 |
> other packages that need python2_7 will whine. |
| 26 |
> |
| 27 |
> Did setuptools-45.0.0 remove all python2 support? I looked at the |
| 28 |
> commit |
| 29 |
> log, and it's only the title that any meaningful hint that it may |
| 30 |
> have, |
| 31 |
> "dev-python/setuptools: Bump to 45.0.0 (py3 only)". If it did, then |
| 32 |
> that |
| 33 |
> change is the right change, but anyone with a userland that has a mix |
| 34 |
> of |
| 35 |
> python2 and python3 is going to have difficulty getting that update |
| 36 |
> to merge |
| 37 |
> in, so I really can't go higher than setuptools-44.0.0 for the time |
| 38 |
> being. |
| 39 |
> |
| 40 |
|
| 41 |
https://setuptools.readthedocs.io/en/latest/history.html#v45-0-0 |
Archives