You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Arvind Kandpal via dev <de...@cassandra.apache.org> on 2026/03/10 06:32:31 UTC
[DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Hi everyone,
I have been working on CASSANDRA-20997 to add support for Python 3.12 and
3.13.
As part of this ticket, we found that simply relaxing the version checks in
cqlsh fails because the asyncore module was removed in Python 3.12. To fix
this, I have raised a PR that fetches the official pyasyncore package as a
dependency and places it in the lib/ directory as a stopgap solution until
the asyncio reactor becomes the default.
The PR is ready, but Stefan Miklosovic suggested bringing this to the
mailing list to figure out the target branches.
Should this fix be merged into *trunk only*, or is there a preference to
backport this Python 3.12/3.13 support to *5.0* (and potentially older
supported branches like *4.1* or *4.0*)?
Looking forward to your feedback.
Thanks,
--
[image: ksolves-logo]
Arvind Kandpal
Junior Software Engineer
[image: phone] (+91) 9650266413 <(+91)+9650266413>
Noida, India www.ksolves.com
[image: Great Place To Work Certified]
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Ekaterina Dimitrova <e....@gmail.com>.
Thanks Arvind, and to everyone else who helped with reviews, etc!
Appreciated!!
On Fri, 3 Jul 2026 at 5:23, Štefan Miklošovič <sm...@apache.org>
wrote:
> It has been a while but we have just merged CASSANDRA-20997 so Python
> 3.12 / 3.13 support will be available in 5.0.9, 6.0-alpha2 (and
> trunk) for the first time.
>
> Kudos to Arvind for this!
>
> On Wed, Mar 11, 2026 at 4:23 PM Štefan Miklošovič
> <sm...@apache.org> wrote:
> >
> > Thanks all, 5.0 and trunk it is.
> >
> > On Tue, Mar 10, 2026 at 5:58 PM Paulo Motta <pa...@apache.org> wrote:
> > >
> > > +1 to 5.0
> > >
> > > On Tue, 10 Mar 2026 at 06:08 Dmitry Konstantinov <ne...@gmail.com>
> wrote:
> > >>
> > >> +1 for 5.0
> > >> Python 3.11 is EOL 2027-10, and I suppose 5.0 will live longer.
> > >>
> > >> On Tue, 10 Mar 2026 at 10:03, Mick <mc...@apache.org> wrote:
> > >>>
> > >>> >
> > >>> > If this could be backported at least to 5.0 it would help with
> this.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> +1
> > >>>
> > >>
> > >>
> > >> --
> > >> Dmitry Konstantinov
>
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Štefan Miklošovič <sm...@apache.org>.
It has been a while but we have just merged CASSANDRA-20997 so Python
3.12 / 3.13 support will be available in 5.0.9, 6.0-alpha2 (and
trunk) for the first time.
Kudos to Arvind for this!
On Wed, Mar 11, 2026 at 4:23 PM Štefan Miklošovič
<sm...@apache.org> wrote:
>
> Thanks all, 5.0 and trunk it is.
>
> On Tue, Mar 10, 2026 at 5:58 PM Paulo Motta <pa...@apache.org> wrote:
> >
> > +1 to 5.0
> >
> > On Tue, 10 Mar 2026 at 06:08 Dmitry Konstantinov <ne...@gmail.com> wrote:
> >>
> >> +1 for 5.0
> >> Python 3.11 is EOL 2027-10, and I suppose 5.0 will live longer.
> >>
> >> On Tue, 10 Mar 2026 at 10:03, Mick <mc...@apache.org> wrote:
> >>>
> >>> >
> >>> > If this could be backported at least to 5.0 it would help with this.
> >>>
> >>>
> >>>
> >>>
> >>> +1
> >>>
> >>
> >>
> >> --
> >> Dmitry Konstantinov
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Štefan Miklošovič <sm...@apache.org>.
Thanks all, 5.0 and trunk it is.
On Tue, Mar 10, 2026 at 5:58 PM Paulo Motta <pa...@apache.org> wrote:
>
> +1 to 5.0
>
> On Tue, 10 Mar 2026 at 06:08 Dmitry Konstantinov <ne...@gmail.com> wrote:
>>
>> +1 for 5.0
>> Python 3.11 is EOL 2027-10, and I suppose 5.0 will live longer.
>>
>> On Tue, 10 Mar 2026 at 10:03, Mick <mc...@apache.org> wrote:
>>>
>>> >
>>> > If this could be backported at least to 5.0 it would help with this.
>>>
>>>
>>>
>>>
>>> +1
>>>
>>
>>
>> --
>> Dmitry Konstantinov
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Paulo Motta <pa...@apache.org>.
+1 to 5.0
On Tue, 10 Mar 2026 at 06:08 Dmitry Konstantinov <ne...@gmail.com> wrote:
> +1 for 5.0
> Python 3.11 is EOL 2027-10, and I suppose 5.0 will live longer.
>
> On Tue, 10 Mar 2026 at 10:03, Mick <mc...@apache.org> wrote:
>
>> >
>> > If this could be backported at least to 5.0 it would help with this.
>>
>>
>>
>>
>> +1
>>
>>
>
> --
> Dmitry Konstantinov
>
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Dmitry Konstantinov <ne...@gmail.com>.
+1 for 5.0
Python 3.11 is EOL 2027-10, and I suppose 5.0 will live longer.
On Tue, 10 Mar 2026 at 10:03, Mick <mc...@apache.org> wrote:
> >
> > If this could be backported at least to 5.0 it would help with this.
>
>
>
>
> +1
>
>
--
Dmitry Konstantinov
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Mick <mc...@apache.org>.
>
> If this could be backported at least to 5.0 it would help with this.
+1
Re: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Posted by Tommy Stendahl via dev <de...@cassandra.apache.org>.
Hi,
Thanks for working on this, its appreciated.
I'm sure we are not the only once with production environments that like to upgrade from Python 3.11. If this could be backported at least to 5.0 it would help with this.
Regards,
/Tommy
-----Original Message-----
From: Arvind Kandpal via dev <dev@cassandra.apache.org<mailto:Arvind%20Kandpal%20via%20dev%20%3cdev@cassandra.apache.org%3e>>
Reply-To: dev@cassandra.apache.org<ma...@cassandra.apache.org>
To: dev@cassandra.apache.org<ma...@cassandra.apache.org>
Cc: Arvind Kandpal <arvind.kandpal@ksolves.com<mailto:Arvind%20Kandpal%20%3carvind.kandpal@ksolves.com%3e>>
Subject: [DISCUSS] Target branches for Python 3.12/3.13 support in cqlsh (CASSANDRA-20997)
Date: Tue, 10 Mar 2026 12:02:31 +0530
Hi everyone,
I have been working on CASSANDRA-20997 to add support for Python 3.12 and 3.13.
As part of this ticket, we found that simply relaxing the version checks in cqlsh fails because the asyncore module was removed in Python 3.12. To fix this, I have raised a PR that fetches the official pyasyncore package as a dependency and places it in the lib/ directory as a stopgap solution until the asyncio reactor becomes the default.
The PR is ready, but Stefan Miklosovic suggested bringing this to the mailing list to figure out the target branches.
Should this fix be merged into trunk only, or is there a preference to backport this Python 3.12/3.13 support to 5.0 (and potentially older supported branches like 4.1 or 4.0)?
Looking forward to your feedback.
Thanks,
--
[https://lh3.googleusercontent.com/a/ACg8ocItr9QFLImBpdzRgJTh39PzXqLdu8rvfxw9JxZ4Qv2a-L2ajKs=s288-c-no][ksolves-logo]
Arvind Kandpal
Junior Software Engineer
[phone] (+91) 9650266413<tel:(+91)+9650266413>
[https://www.ksolves.com/assets/icon2/location.png] Noida, India [https://www.ksolves.com/assets/icon2/globe.png] www.ksolves.com<https://www.ksolves.com/>
[https://www.ksolves.com/wp-content/uploads/2026/02/updated-partner.png]
[Great Place To Work Certified]