> > 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 I have to install it?". The cost of keeping support is a small amount of drag as we consider fixing bugs and maintaining compatibility. It's not huge, but I don't see a lot of reasons to incur it. 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. This would just guide us in deciding whether to work on flaws that are python2-specific, and whether new things are developed with backwards compatibility as a forcing concern. I'll have to catch up on the other ticket and see what bearing it has on this discussion. On Tue, Jan 26, 2021 at 1:46 AM Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> wrote: > +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 <yc25c...@gmail.com> wrote: > > > +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 < > e.dimitr...@gmail.com > > > > > wrote: > > > > > I support the idea, we are not removing python2-compatible code > > > +1 > > > > > > On Fri, 22 Jan 2021 at 15:14, Adam Holmberg < > adam.holmb...@datastax.com> > > > 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 sunsetted (a year ago [2]). I hadn't seen a > > > > discussion about whether we intend to carry on support for Python 2, > so > > > I'm > > > > raising one here. > > > > > > > > 4.0 is a major release and we have an opportunity to drop support at > > this > > > > milestone. It has been mentioned that it will not be acceptable to do > > in > > > a > > > > minor or patch release, so if it's not done for 4.0, we will need to > > wait > > > > for the next major. I do understand that many in the project would > like > > > > majors on a more frequent interval post-4.0, but at this time we > don't > > > know > > > > when that will be. > > > > > > > > I advocate for dropping support ASAP. I expect that users should not > be > > > > inconvenienced by this -- I am not aware of a major distro that has > not > > > had > > > > python3 for years. Dropping python2 support does not mean that we > would > > > do > > > > work to rip out python2-compatible code, just that we wouldn't > > advertise > > > > support and any package requirements would be adjusted. We benefit by > > > > removing the need to test multiple runtimes, and we wouldn't be > > concerned > > > > with fixing python2-specific issues that may arise on the EOL runtime > > > [3]. > > > > > > > > I look forward to the discussion. > > > > > > > > -- > > > > Adam Holmberg > > > > e. adam.holmb...@datastax.com > > > > w. www.datastax.com > > > > > > > > [1] https://issues.apache.org/jira/browse/CASSANDRA-10190 > > > > [2] > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.python.org_doc_sunset-2Dpython-2D2_&d=DwIBaQ&c=adz96Xi0w1RHqtPMowiL2g&r=GgOKQUoTLCKbKh1M_uCZ-t7CW3HHZHE_I4OFzjDOiIs&m=PHNtl_WeGlGcuZQ1iwiajdr1eBZpuu1uxx8Ty-LCtiw&s=dDf0vhcr06PYYRjqcO9iwAWvN109cwYQNF6k9odIMIs&e= > > > > [3] https://issues.apache.org/jira/browse/CASSANDRA-16400 > > > > > > > > > > -- Adam Holmberg e. adam.holmb...@datastax.com w. www.datastax.com
