Re: Dropping Python 3.6 support in 4.1
This. RHEL8 is going to be around for a long while, so I'd say python-3.6 should not be dropped for a long while. 2029 EOL is the date I see on the RHEL8 Planning Guide[0].. I saw the RHEL7/CentOS7 comments earlier and immediately thought about RHEL8 and python-3.6, since I'm working in that OS environment lately, along with C* being one small component of the system.. [0] https://access.redhat.com/support/policy/updates/errata Kind regards, Michael On 4/6/22 11:13, Gerald Henriksen wrote: On Tue, 5 Apr 2022 12:20:49 +0100, you wrote: I would strongly recommend keeping Python 3.6 compatibility until 2024-06-30 when the CentOS 7 maintenance updates is stopped. I would point out that the RHEL 8.* (as seen on Rocky Linux 8.5) releases come with Python 3.6 and I don't see anything newer in the EPEL repository for the 8.* series of releases.
Re: Dropping Python 3.6 support in 4.1
On Tue, 5 Apr 2022 12:20:49 +0100, you wrote: >I would strongly recommend keeping Python 3.6 compatibility until >2024-06-30 when the CentOS 7 maintenance updates is stopped. I would point out that the RHEL 8.* (as seen on Rocky Linux 8.5) releases come with Python 3.6 and I don't see anything newer in the EPEL repository for the 8.* series of releases.
Re: Dropping Python 3.6 support in 4.1
We still mostly support CentOS 6 =D, I say mostly due to the fact I am not aware of any formal supports, just informal patches getting older OSes working again. > On Apr 5, 2022, at 4:33 AM, Stefan Miklosovic > wrote: > > But ... this begs another question to be asked - until when we want to > support Centos 7 ? > > On Tue, 5 Apr 2022 at 13:31, Stefan Miklosovic > wrote: >> >> All good then, that's why I am asking! >> >> Thanks >> >> On Tue, 5 Apr 2022 at 13:23, Brandon Williams wrote: >>> >>> This changes my mind and I agree. >>> >>> On Tue, Apr 5, 2022 at 6:21 AM Bowen Song wrote: I'm against this change. CentOS 7 only has Python up to 3.6 available from the EPEL repository, and the maintenance updates for CentOS 7 ends in 2024. See: https://wiki.centos.org/About/Product To install Python>3.6 on CentOS 7, the user must either use a 3rd party repository that's not maintained by the same project or compile it from source. None of these is as simple as "yum install epel-release && yum install python36". I would strongly recommend keeping Python 3.6 compatibility until 2024-06-30 when the CentOS 7 maintenance updates is stopped. On 05/04/2022 11:35, Stefan Miklosovic wrote: > Hello, > > I stumbled upon this ticket (1) > > We will have Cassandra running with unsupported Python 3.6 once we > release 4.1 which is not good in my books. > > I would like to try to bump it to 3.8 as minimum, it will get security > updates to 2024 at least. > > Does it make sense to people? Especially so close to the freeze. I > guess we would need to update Python in Jenkins images mostly and so > on. I am running 3.8.10 locally with all the tests so it really seems > to be just a version bump. > > Regards > > (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Re: Dropping Python 3.6 support in 4.1
But ... this begs another question to be asked - until when we want to support Centos 7 ? On Tue, 5 Apr 2022 at 13:31, Stefan Miklosovic wrote: > > All good then, that's why I am asking! > > Thanks > > On Tue, 5 Apr 2022 at 13:23, Brandon Williams wrote: > > > > This changes my mind and I agree. > > > > On Tue, Apr 5, 2022 at 6:21 AM Bowen Song wrote: > > > > > > I'm against this change. > > > > > > CentOS 7 only has Python up to 3.6 available from the EPEL repository, > > > and the maintenance updates for CentOS 7 ends in 2024. See: > > > https://wiki.centos.org/About/Product > > > > > > To install Python>3.6 on CentOS 7, the user must either use a 3rd party > > > repository that's not maintained by the same project or compile it from > > > source. None of these is as simple as "yum install epel-release && yum > > > install python36". > > > > > > I would strongly recommend keeping Python 3.6 compatibility until > > > 2024-06-30 when the CentOS 7 maintenance updates is stopped. > > > > > > On 05/04/2022 11:35, Stefan Miklosovic wrote: > > > > Hello, > > > > > > > > I stumbled upon this ticket (1) > > > > > > > > We will have Cassandra running with unsupported Python 3.6 once we > > > > release 4.1 which is not good in my books. > > > > > > > > I would like to try to bump it to 3.8 as minimum, it will get security > > > > updates to 2024 at least. > > > > > > > > Does it make sense to people? Especially so close to the freeze. I > > > > guess we would need to update Python in Jenkins images mostly and so > > > > on. I am running 3.8.10 locally with all the tests so it really seems > > > > to be just a version bump. > > > > > > > > Regards > > > > > > > > (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Re: Dropping Python 3.6 support in 4.1
All good then, that's why I am asking! Thanks On Tue, 5 Apr 2022 at 13:23, Brandon Williams wrote: > > This changes my mind and I agree. > > On Tue, Apr 5, 2022 at 6:21 AM Bowen Song wrote: > > > > I'm against this change. > > > > CentOS 7 only has Python up to 3.6 available from the EPEL repository, > > and the maintenance updates for CentOS 7 ends in 2024. See: > > https://wiki.centos.org/About/Product > > > > To install Python>3.6 on CentOS 7, the user must either use a 3rd party > > repository that's not maintained by the same project or compile it from > > source. None of these is as simple as "yum install epel-release && yum > > install python36". > > > > I would strongly recommend keeping Python 3.6 compatibility until > > 2024-06-30 when the CentOS 7 maintenance updates is stopped. > > > > On 05/04/2022 11:35, Stefan Miklosovic wrote: > > > Hello, > > > > > > I stumbled upon this ticket (1) > > > > > > We will have Cassandra running with unsupported Python 3.6 once we > > > release 4.1 which is not good in my books. > > > > > > I would like to try to bump it to 3.8 as minimum, it will get security > > > updates to 2024 at least. > > > > > > Does it make sense to people? Especially so close to the freeze. I > > > guess we would need to update Python in Jenkins images mostly and so > > > on. I am running 3.8.10 locally with all the tests so it really seems > > > to be just a version bump. > > > > > > Regards > > > > > > (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Re: Dropping Python 3.6 support in 4.1
This changes my mind and I agree. On Tue, Apr 5, 2022 at 6:21 AM Bowen Song wrote: > > I'm against this change. > > CentOS 7 only has Python up to 3.6 available from the EPEL repository, > and the maintenance updates for CentOS 7 ends in 2024. See: > https://wiki.centos.org/About/Product > > To install Python>3.6 on CentOS 7, the user must either use a 3rd party > repository that's not maintained by the same project or compile it from > source. None of these is as simple as "yum install epel-release && yum > install python36". > > I would strongly recommend keeping Python 3.6 compatibility until > 2024-06-30 when the CentOS 7 maintenance updates is stopped. > > On 05/04/2022 11:35, Stefan Miklosovic wrote: > > Hello, > > > > I stumbled upon this ticket (1) > > > > We will have Cassandra running with unsupported Python 3.6 once we > > release 4.1 which is not good in my books. > > > > I would like to try to bump it to 3.8 as minimum, it will get security > > updates to 2024 at least. > > > > Does it make sense to people? Especially so close to the freeze. I > > guess we would need to update Python in Jenkins images mostly and so > > on. I am running 3.8.10 locally with all the tests so it really seems > > to be just a version bump. > > > > Regards > > > > (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Re: Dropping Python 3.6 support in 4.1
I'm against this change. CentOS 7 only has Python up to 3.6 available from the EPEL repository, and the maintenance updates for CentOS 7 ends in 2024. See: https://wiki.centos.org/About/Product To install Python>3.6 on CentOS 7, the user must either use a 3rd party repository that's not maintained by the same project or compile it from source. None of these is as simple as "yum install epel-release && yum install python36". I would strongly recommend keeping Python 3.6 compatibility until 2024-06-30 when the CentOS 7 maintenance updates is stopped. On 05/04/2022 11:35, Stefan Miklosovic wrote: Hello, I stumbled upon this ticket (1) We will have Cassandra running with unsupported Python 3.6 once we release 4.1 which is not good in my books. I would like to try to bump it to 3.8 as minimum, it will get security updates to 2024 at least. Does it make sense to people? Especially so close to the freeze. I guess we would need to update Python in Jenkins images mostly and so on. I am running 3.8.10 locally with all the tests so it really seems to be just a version bump. Regards (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Re: Dropping Python 3.6 support in 4.1
"We will have Cassandra running with unsupported Python 3.6 once we release 4.1" - what I meant by that that if somebody has Python 3.6, it will be possible to run cqlsh. There is a check, afaik, which checks what Python a user has and it prevents them from running it if it is something lower. https://github.com/apache/cassandra/blob/trunk/bin/cqlsh.py#L38-L39 On Tue, 5 Apr 2022 at 12:35, Stefan Miklosovic wrote: > > Hello, > > I stumbled upon this ticket (1) > > We will have Cassandra running with unsupported Python 3.6 once we > release 4.1 which is not good in my books. > > I would like to try to bump it to 3.8 as minimum, it will get security > updates to 2024 at least. > > Does it make sense to people? Especially so close to the freeze. I > guess we would need to update Python in Jenkins images mostly and so > on. I am running 3.8.10 locally with all the tests so it really seems > to be just a version bump. > > Regards > > (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
Dropping Python 3.6 support in 4.1
Hello, I stumbled upon this ticket (1) We will have Cassandra running with unsupported Python 3.6 once we release 4.1 which is not good in my books. I would like to try to bump it to 3.8 as minimum, it will get security updates to 2024 at least. Does it make sense to people? Especially so close to the freeze. I guess we would need to update Python in Jenkins images mostly and so on. I am running 3.8.10 locally with all the tests so it really seems to be just a version bump. Regards (1) https://issues.apache.org/jira/browse/CASSANDRA-17450
