+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
+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
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
I confirm we're almost done with CASSANDRA-15580 (Repair QA testing).
Nightly runs are scheduled already and I'm tuning some knobs to get them
nicely stable:
https://app.circleci.com/pipelines/github/riptano/cassandra-rtest?branch=trunk
Andres also created an in-jvm dtest for the mixed cluster
+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
