[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481694#comment-17481694 ] Berenguer Blasi edited comment on CASSANDRA-17242 at 1/25/22, 10:00 AM: If I didn't miss anything: - I think we're missing fixing the high res patch unless it does still apply cleanly? That would be suspicious imo - Was the MID CI run config manually edited or generated? I will assume it was generated but just doublechecking. - We only have a CI run for MID. I would suggested generating LOW and HIGH CI runs as well to make sure we don't merge sthg it fails frist time we run HIGH i.e. - Do we need to update dtests docs to use pip3 instead of pip? My 2cts was (Author: bereng): If I didn't miss anything: - I think we're missing fixing the high res patch unless it does still apply cleanly? That would be suspicious imo - Was the MID CI run config manually edited or generated? I will assume it was generated but just doublechecking. - We only have a CI run for MID. I would suggested generating LOW and HIGH CI runs as well to make sure we don't merge sthg it fails frist time we run HIGH i.e. My 2cts > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479596#comment-17479596 ] Brandon Williams edited comment on CASSANDRA-17242 at 1/20/22, 7:09 PM: No worries, it was tagged 4.0.x earlier, you probably caught that update. Adding a jenkins run to see if anything needs to be disabled there. [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1373/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1373/pipeline] was (Author: brandon.williams): No worries, it was tagged 4.0.x earlier, you probably caught that update. Adding a jenkins run to see if anything needs to be disabled there. [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1372/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1372/pipeline] > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479543#comment-17479543 ] Brandon Williams edited comment on CASSANDRA-17242 at 1/20/22, 5:47 PM: It does target trunk? I'm not planning to remove it from 4.0 for reasons that you stated. was (Author: brandon.williams): It does target trunk? > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479534#comment-17479534 ] Ekaterina Dimitrova edited comment on CASSANDRA-17242 at 1/20/22, 5:28 PM: --- Quick question - shouldn't this target only trunk? I feel that was intentionally still there in 4.0. I think that cutting it in a patch release is not a good idea and contradicts with the release process probably was (Author: e.dimitrova): Quick question - shouldn't this target only trunk? > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479530#comment-17479530 ] Brandon Williams edited comment on CASSANDRA-17242 at 1/20/22, 5:21 PM: This looks good and I'm +1, but need to figure out how to disable the py2 dtest runs for trunk. was (Author: brandon.williams): This looks good and I'm +1, but need to figure out how to disable the py2 dtest runs for 4.0 and trunk. > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > Fix For: 4.x > > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470827#comment-17470827
]
Brad Schoening edited comment on CASSANDRA-17242 at 1/7/22, 11:00 PM:
--
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x. Python 2.7 its deprecated, but still supported, unless I'm
misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib code imports 'six' for cross-compatibility instead of using
native python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
was (Author: bschoeni):
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x, but 2.7 its deprecated, unless I'm misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib code imports 'six' for cross-compatibility instead of using
native python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
> Remove Python 2.x support from CQLSH
>
>
> Key: CASSANDRA-17242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17242
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Python 2 has now reached EOL and should be removed from CQLSH and other
> Cassandra components.
> "We are volunteers who make and take care of the Python programming language.
> We have decided that January 1, 2020, was the day that we sunset Python 2.
> That means that we will not improve it anymore after that day, even if
> someone finds a security problem in it. You should upgrade to Python 3 as
> soon as you can.
> And if many people keep using Python 2, then that makes it hard for [the
> volunteers who use Python to make
> software|https://python3statement.org/#sections50-why]. They can't use the
> good new things in Python 3 to improve the tools they make.
> As of January 1st, 2020 no new bug reports, fixes, or changes will be made to
> Python 2, and Python 2 is no longer supported.
> "
> [https://www.python.org/doc/sunset-python-2/]
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470827#comment-17470827
]
Brad Schoening edited comment on CASSANDRA-17242 at 1/7/22, 7:24 PM:
-
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x, but 2.7 its deprecated, unless I'm misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib code imports 'six' for cross-compatibility instead of using
native python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
was (Author: bschoeni):
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x, but 2.7 its deprecated, unless I'm misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib imports 'six' for cross-compatibility instead of using native
python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
> Remove Python 2.x support from CQLSH
>
>
> Key: CASSANDRA-17242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17242
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Python 2 has now reached EOL and should be removed from CQLSH and other
> Cassandra components.
> "We are volunteers who make and take care of the Python programming language.
> We have decided that January 1, 2020, was the day that we sunset Python 2.
> That means that we will not improve it anymore after that day, even if
> someone finds a security problem in it. You should upgrade to Python 3 as
> soon as you can.
> And if many people keep using Python 2, then that makes it hard for [the
> volunteers who use Python to make
> software|https://python3statement.org/#sections50-why]. They can't use the
> good new things in Python 3 to improve the tools they make.
> As of January 1st, 2020 no new bug reports, fixes, or changes will be made to
> Python 2, and Python 2 is no longer supported.
> "
> [https://www.python.org/doc/sunset-python-2/]
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470827#comment-17470827
]
Brad Schoening edited comment on CASSANDRA-17242 at 1/7/22, 7:04 PM:
-
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x, but 2.7 its deprecated, unless I'm misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib imports 'six' for cross-compatibility instead of using native
python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
was (Author: bschoeni):
Thanks for your quick reply. The code in cqlsy.py states it supports python 2.7
AND python 3.x, but its deprecated, unless I'm misreading it.
if sys.version_info < (3, 6) and sys.version_info[0:2] != (2, 7):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+ or Python 2.7 (deprecated)\n")
and the cqlshlib imports 'six' for cross-compatibility instead of using native
python 3.x constructs.
If the intention is to no longer support python 2.7, the above should be simply
changed to exit if sys.version_info is less than 3.6
if sys.version_info < (3, 6):
[
|https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob;f=bin/cqlsh.py;h=aa005ce95233415a8e4a3d99fb27ebe170da0b26;hb=HEAD#l40]
sys.exit("\ncqlsh requires Python 3.6+\n")
> Remove Python 2.x support from CQLSH
>
>
> Key: CASSANDRA-17242
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17242
> Project: Cassandra
> Issue Type: Task
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> Python 2 has now reached EOL and should be removed from CQLSH and other
> Cassandra components.
> "We are volunteers who make and take care of the Python programming language.
> We have decided that January 1, 2020, was the day that we sunset Python 2.
> That means that we will not improve it anymore after that day, even if
> someone finds a security problem in it. You should upgrade to Python 3 as
> soon as you can.
> And if many people keep using Python 2, then that makes it hard for [the
> volunteers who use Python to make
> software|https://python3statement.org/#sections50-why]. They can't use the
> good new things in Python 3 to improve the tools they make.
> As of January 1st, 2020 no new bug reports, fixes, or changes will be made to
> Python 2, and Python 2 is no longer supported.
> "
> [https://www.python.org/doc/sunset-python-2/]
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470748#comment-17470748 ] Brad Schoening edited comment on CASSANDRA-17242 at 1/7/22, 4:52 PM: - The Cassandra 4.0.x CQLSH code is still backwards compatible with python 2.7. This Jira is to suggest remove support for python 2.x entirely. " cqlsh support of 2.7 is deprecated and will warn when running with Python 2.7" in cqlsh.py Python 2.x support is undesirable for several reasons a) Python 3 features can't be used unless they've been backported to python 2.7, so the Cassandra python code base can't be modernized while still supporting 2.7 b) Changes require testing with both python 3.x and 2.7; most contributors don't have a python 2.x environment anymore by default. c) There are known security vulnerabilities in python 2.7 which are not being patched now that it is EOL. Some of the known ones are [CVE-2021-23336|https://nvd.nist.gov/vuln/detail/CVE-2021-23336], [CVE-2021-3177|https://nvd.nist.gov/vuln/detail/CVE-2021-3177], [CVE-2020-27619|https://nvd.nist.gov/vuln/detail/CVE-2020-27619], [CVE-2020-26116|https://nvd.nist.gov/vuln/detail/CVE-2020-26116], [CVE-2019-20907|https://nvd.nist.gov/vuln/detail/CVE-2019-20907], [CVE-2020-8492|https://nvd.nist.gov/vuln/detail/CVE-2020-8492] (according to a list at [Python 2 Security Vulnerability (CVE) Updates - Extended Support (activestate.com) )|https://www.activestate.com/products/python/python-2-end-of-life-security-updates/] was (Author: bschoeni): The Cassandra 4.0.x CQLSH code is still backwards compatible with python 2.7. This Jira is to suggest remove support for python 2.x entirely. " cqlsh support of 2.7 is deprecated and will warn when running with Python 2.7" in cqlsh.py This is undesirable for several reasons a) Python 3 features can't be used unless they've been backported to python 2.7, so the Cassandra python code base can't be modernized while still supporting 2.7 b) Changes require testing with both python 3.x and 2.7; most contributors don't have a python 2.x environment anymore by default. c) There are known security vulnerabilities in python 2.7 which are not being patched now that it is EOL. Some of the known ones are [CVE-2021-23336|https://nvd.nist.gov/vuln/detail/CVE-2021-23336], [CVE-2021-3177|https://nvd.nist.gov/vuln/detail/CVE-2021-3177], [CVE-2020-27619|https://nvd.nist.gov/vuln/detail/CVE-2020-27619], [CVE-2020-26116|https://nvd.nist.gov/vuln/detail/CVE-2020-26116], [CVE-2019-20907|https://nvd.nist.gov/vuln/detail/CVE-2019-20907], [CVE-2020-8492|https://nvd.nist.gov/vuln/detail/CVE-2020-8492] (according to a list at [Python 2 Security Vulnerability (CVE) Updates - Extended Support (activestate.com) )|https://www.activestate.com/products/python/python-2-end-of-life-security-updates/] > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17242) Remove Python 2.x support from CQLSH
[ https://issues.apache.org/jira/browse/CASSANDRA-17242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470748#comment-17470748 ] Brad Schoening edited comment on CASSANDRA-17242 at 1/7/22, 4:51 PM: - The Cassandra 4.0.x CQLSH code is still backwards compatible with python 2.7. This Jira is to suggest remove support for python 2.x entirely. " cqlsh support of 2.7 is deprecated and will warn when running with Python 2.7" in cqlsh.py This is undesirable for several reasons a) Python 3 features can't be used unless they've been backported to python 2.7, so the Cassandra python code base can't be modernized while still supporting 2.7 b) Changes require testing with both python 3.x and 2.7; most contributors don't have a python 2.x environment anymore by default. c) There are known security vulnerabilities in python 2.7 which are not being patched now that it is EOL. Some of the known ones are [CVE-2021-23336|https://nvd.nist.gov/vuln/detail/CVE-2021-23336], [CVE-2021-3177|https://nvd.nist.gov/vuln/detail/CVE-2021-3177], [CVE-2020-27619|https://nvd.nist.gov/vuln/detail/CVE-2020-27619], [CVE-2020-26116|https://nvd.nist.gov/vuln/detail/CVE-2020-26116], [CVE-2019-20907|https://nvd.nist.gov/vuln/detail/CVE-2019-20907], [CVE-2020-8492|https://nvd.nist.gov/vuln/detail/CVE-2020-8492] (according to a list at [Python 2 Security Vulnerability (CVE) Updates - Extended Support (activestate.com) )|https://www.activestate.com/products/python/python-2-end-of-life-security-updates/] was (Author: bschoeni): The Cassandra 4.0.x CQLSH code is still backwards compatible with python 2.7. " cqlsh support of 2.7 is deprecated and will warn when running with Python 2.7" in cqlsh.py This is undesirable for several reasons a) Python 3 features can't be used unless they've been backported to python 2.7, so the Cassandra python code base can't be modernized while still supporting 2.7 b) Changes require testing with both python 3.x and 2.7; most contributors don't have a python 2.x environment anymore by default. c) There are known security vulnerabilities in python 2.7 which are not being patched now that it is EOL. Some of the known ones are [CVE-2021-23336|https://nvd.nist.gov/vuln/detail/CVE-2021-23336], [CVE-2021-3177|https://nvd.nist.gov/vuln/detail/CVE-2021-3177], [CVE-2020-27619|https://nvd.nist.gov/vuln/detail/CVE-2020-27619], [CVE-2020-26116|https://nvd.nist.gov/vuln/detail/CVE-2020-26116], [CVE-2019-20907|https://nvd.nist.gov/vuln/detail/CVE-2019-20907], [CVE-2020-8492|https://nvd.nist.gov/vuln/detail/CVE-2020-8492] (according to a list at [Python 2 Security Vulnerability (CVE) Updates - Extended Support (activestate.com) )|https://www.activestate.com/products/python/python-2-end-of-life-security-updates/] > Remove Python 2.x support from CQLSH > > > Key: CASSANDRA-17242 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17242 > Project: Cassandra > Issue Type: Task > Components: CQL/Interpreter >Reporter: Brad Schoening >Priority: Normal > > Python 2 has now reached EOL and should be removed from CQLSH and other > Cassandra components. > "We are volunteers who make and take care of the Python programming language. > We have decided that January 1, 2020, was the day that we sunset Python 2. > That means that we will not improve it anymore after that day, even if > someone finds a security problem in it. You should upgrade to Python 3 as > soon as you can. > And if many people keep using Python 2, then that makes it hard for [the > volunteers who use Python to make > software|https://python3statement.org/#sections50-why]. They can't use the > good new things in Python 3 to improve the tools they make. > As of January 1st, 2020 no new bug reports, fixes, or changes will be made to > Python 2, and Python 2 is no longer supported. > " > [https://www.python.org/doc/sunset-python-2/] > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
