| 1 |
On Mon, 10 Dec 2018, Michał Górny wrote: |
| 2 |
> Now, IPython is now split upstream into two branches: 5 and 6. The old |
| 3 |
> branch 5 supports py2+py3 which is good. The new branch 6 supports py3 |
| 4 |
> only. This means that any IPython revdep that requires py2 needs to |
| 5 |
> force the old branch. |
| 6 |
The current version is 7.2 already. The branch 7 is py3 only, of course. |
| 7 |
|
| 8 |
> Unless someone has a better idea, I think a combined b+c approach might |
| 9 |
> be the way to go. That is: |
| 10 |
> |
| 11 |
> 1. slot IPython as described above. |
| 12 |
> |
| 13 |
> 2. update py2+py3 revdeps to use proper cond-dep for slotted version. |
| 14 |
> |
| 15 |
> 3. slowly drop py2 from revdeps whenever possible. |
| 16 |
Seems reasonable. I'm eager to try ipython-7.x. |
| 17 |
|
| 18 |
Another similar case is matplotlib. The branch 3 (not yet in our tree) is |
| 19 |
py3 only. Probably, other major projects will become py3-only soon. |
| 20 |
|
| 21 |
For example, I use py3 whenever I can. But I use a few py2-only |
| 22 |
packages, such as dev-util/diffuse (a very nice gui diff/merge tool, based |
| 23 |
on pygtk, the latest release in 2014). I hope py2.7 and simple py2-only |
| 24 |
packages without numerous deps (like diffuse) will live in the tree for a |
| 25 |
long enough time. |
| 26 |
|
| 27 |
Andrey |
Archives