Re: [DISCUSS] When to stop supporting Python 2

Thanks for the discussion and input. It seems like this thread has run its course, so I'm hoping to bring it to a close with the following: for 4.0: - Update documentation removing any claim of support for Python2 (but do not actually break). Introduce warning when running in Python 2.7. I

Re: [DISCUSS] When to stop supporting Python 2

>From the "Supported upgrade path for 4.0" discussion, it seems like there was consensus around supporting the "3.0 -> 4.0" upgrade path as well (in addition to 3.11 -> 4.0), so we may need to add python3 support for 3.0 as well? Internally. we had a need to make 3.0 cqlsh python3 compatible, and

Re: [DISCUSS] When to stop supporting Python 2

Considering the issue with pip. I agree that we should remove support for 3.0 and ensure that python 3 is supported by 3.11. On Wed, Jan 27, 2021 at 8:18 PM Jonathan Ellis wrote: > Python 2 was EOLed over a year ago. I think it's fine to (1) require > python 3 to run cqlsh and (2) remove code

Re: [DISCUSS] When to stop supporting Python 2

Python 2 was EOLed over a year ago. I think it's fine to (1) require python 3 to run cqlsh and (2) remove code that supports python 2 whenever it's convenient. Angelo has the right idea that rather than trying to finesse a deprecation cycle into 4.0 at this late date, a better migration path can

Re: [DISCUSS] When to stop supporting Python 2

On Wed, Jan 27, 2021 at 12:09 PM Adam Holmberg wrote: > I want to emphasize here: to my way of thinking, "dropping support" at this > juncture is just a matter of documenting it, and maybe introducing a > warning. We don't need to *remove* support for python2. It will continue to > work as-is.

Re: [DISCUSS] When to stop supporting Python 2

> > Does anybody know what are the practicalities/hurdles > that users can face when upgrading and what is the expected cost of keeping > support for 2.7 until the next major? > Given that the code supports both, the only barrier to the user is "does my distro have python3 (most likely), or would

Re: [DISCUSS] When to stop supporting Python 2

While discussing with Mick in an external discussion, he raised the fact that the project approach has always been to deprecate features/support in one major version and remove them in the following one. Due to the fact that 4.0 took so long, we did not respect that approach for the Windows

Re: [DISCUSS] When to stop supporting Python 2

According to some study I found here it seems that not all the organizations are ready regarding python 3. I am not a python expert. Does anybody know what are the practicalities/hurdles that users can face when

Re: [DISCUSS] When to stop supporting Python 2

We have a check in CQLSH that prevents it to start if the python version is lower than python 2.7. I am fine dropping support for python 2 as long as we make it explicits in the NEWS.txt and that we add a warning in CQLSH to notify python 2 users that it is not supported anymore and might not work

Re: [DISCUSS] When to stop supporting Python 2

+1 (nb) for dropping support for python2; I agree 4.0 major release is a good time to do this, given python2 is already EOL. On Mon, Jan 25, 2021 at 2:00 PM Yifan Cai wrote: > +1 nb. > We probably also want to set a milestone to get rid of the python2 > compatible code completely, if we are

Re: [DISCUSS] When to stop supporting Python 2

+1 nb. We probably also want to set a milestone to get rid of the python2 compatible code completely, if we are going in the direction that drops python2 support in 4.0 and retains the python2 compatible code. In 4.x or 5.0? On Mon, Jan 25, 2021 at 9:24 AM Ekaterina Dimitrova wrote: > I support

Re: [DISCUSS] When to stop supporting Python 2

I support the idea, we are not removing python2-compatible code +1 On Fri, 22 Jan 2021 at 15:14, Adam Holmberg wrote: > As you may recall, CASSANDRA-10190 [1] introduced Python 3 support for > cqlsh. This change will be landing in 4.0. In the course of development and > discussion spanning

Re: [DISCUSS] When to stop supporting Python 2

+1 On 22/1/21 21:14, Adam Holmberg wrote: > As you may recall, CASSANDRA-10190 [1] introduced Python 3 support for > cqlsh. This change will be landing in 4.0. In the course of development and > discussion spanning years, it was decided to retain support for Python 2. > In the meantime, Python 2

Re: [DISCUSS] When to stop supporting Python 2

Since python2 was completely removed from FreeBSD at the end of 2020, this is a good idea from my perspective. On a related note, since cassandra3 on FreeBSD was facing removal due to the python2 dependency, I back-ported python3 compatibility to the 3.11 branch. I've just created CASSANDRA-16403

[DISCUSS] When to stop supporting Python 2

As you may recall, CASSANDRA-10190 [1] introduced Python 3 support for cqlsh. This change will be landing in 4.0. In the course of development and discussion spanning years, it was decided to retain support for Python 2. In the meantime, Python 2 sunsetted (a year ago [2]). I hadn't seen a