[
https://issues.apache.org/jira/browse/CASSANDRA-17450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518152#comment-17518152
]
Brad Schoening commented on CASSANDRA-17450:
--------------------------------------------
First, I'll note that this issue doesn't have a release version assigned, so
the discussion is not if, but when to sunset support for Python 3.6 which has
reached EOL. Should it be C* 4.2, 4.3, or something else?
It's worth noting that EOL for Cassandra 4.0 is planned for May/July 2024 which
aligns nicely with the RHEL/CentOS lifecycle. Users can continue to use 4.0 or
4.1 with python 3.6 until then.
There are two very real maintenance cost here:
# Developers/contributors will be expected to test, support and investigate
issues/bugs against EOL python versions.
# New language features and libraries in 3.7+ cannot be used. See
[https://www.python.org/downloads/release/python-370] for new features such as
Data Classes and typing.
As a contributor, I find the testing and support complexity more important and
discouraging when the base language used on trunk has reached EOL.
It's worth noting that EOL for Cassandra 4.0 is planned for May/July 2024 which
aligns nicely with the RHEL/CentOS 7 lifecycle. Users can continue to use 4.0
or 4.1 with python 3.6 and remain fully supported with CQLSH on C* 4.0 and 4.1
well past mid-2024.
> Drop python 3.6 support
> -----------------------
>
> Key: CASSANDRA-17450
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17450
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
> Reporter: Brad Schoening
> Priority: Normal
> Fix For: 4.x
>
>
> Python 3.6 became EOL as of 12/23/21. There will be no further releases or
> security fixes for Python 3.6.
> https://github.com/httpie/httpie/issues/1177
> https://devguide.python.org/#status-of-python-branches
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
