> On 10/01/2020, at 11:23 PM, E. Madison Bray <erik.m.b...@gmail.com> wrote:
>
> On Fri, Jan 10, 2020 at 10:41 AM Timo Kaufmann <eisfre...@gmail.com> wrote:
>>
>> I have said this before, but I feel like the point was dropped out of the
>> discussion so I'll stress it again. The major issue here is *not* the
>> compatibility of sage's own codebase. A few "from __future__ import"'s are
>> not so bad.
>>
>> The issue is that python2 compatibility forces us to use outdated versions
>> of a lot of libraries, since many libraries have dropped python2 support a
>> while ago. This is a big headache especially for packagers. Those outdated
>> libraries are generally not available on distros. At the same time sage is
>> usually not compatible with the newer versions. Sage is already difficult to
>> package, and that makes it a lot more difficult.
>
> Can you be more specific about this? What is it about Sage's upstream
> codebase maintaining backwards-compatibility for Python 2 that
> prevents you from packaging it for Python 3 only, given that it does
> support Python 3? No one is saying that just because upstream support
> is maintained for Python 2 for one or two (at the most) more releases,
> any downstream packagers have to package it for Python 2.
We don’t. I only support python3 anymore on gentoo - because support for python2
ipython/jupyter as been removed from the main tree.
I am the lucky one because I still have an ipython-5 I can pull as a dependency,
most of my colleagues have to go ipython-7+ which is python3 only and requires
heavy patching. Some interesting packages we may want to use that are python3
only
and that will make our life difficult because we have to move forward regardless
* ipython-7
* matplotlib-3
* sphinx-2
* numpy-1.17
* scipy-1.3+
The main person that has valid reason to want longer support for python2 is
William.
As he mentions, he has paying customers.
At this point my only reasonable suggestion is to have a python2 compatibility
branch
for a while as sage-9.x while some of us plow on ahead without in sage-10.x.
That’s unreasonable on the release manager unless someone step up to help.
François
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/BBC8CF32-2E9D-4DC0-BBE5-5130E15B3B14%40gmail.com.
