1 |
Hi, |
2 |
|
3 |
As you may have noticed, support for python 2.7 in the ipython stack has been |
4 |
removed from the main tree. |
5 |
Since ipython is an essential part of sage I removed python 2.7 support from |
6 |
all current sage ebuilds. I also removed the old sage notebook as it is a |
7 |
python 2.7 only component. There may be further clean up of the overlay to remove |
8 |
some bits that were only needed for the old sage notebook. |
9 |
|
10 |
Cheers, |
11 |
François |
12 |
|
13 |
> On 19/11/2019, at 10:14 PM, François Bissey <frp.bissey@×××××.com> wrote: |
14 |
> |
15 |
> Hi, |
16 |
> |
17 |
> As many of you surely know, upstream support for python 2.7 is ending in 2020. |
18 |
> Someone else may fill the gap but by and large people have migrated to python3. |
19 |
> sage has slowly been migrating to python 3 over the last couple of years and |
20 |
> sage 9.0 (the next release) will be the first one which default to python3 |
21 |
> (3.7 to be more precise). |
22 |
> |
23 |
> With that being said I am not sure for how long, after the first of January 2020, |
24 |
> Gentoo will support python 2.7. So I have decided that in Gentoo the next release |
25 |
> of sage (9.0) will drop python 2.7. While upstream may cling to it for a bit longer |
26 |
> I want to have a head start on the impeding removal of python 2.7 from the main tree. |
27 |
> |
28 |
> For people following sage-9999 (the next beta release of sage), the drop will |
29 |
> occur in the next release (probably called 9.0.beta7). |
30 |
> |
31 |
> Cheers, |
32 |
> François |