-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Drop python 3.5 #1480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop python 3.5 #1480
Conversation
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: palnabarun, yliaog The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The test is constantly failing due to #1485 |
Signed-off-by: Nabarun Pal <[email protected]>
Signed-off-by: Nabarun Pal <[email protected]>
Signed-off-by: Nabarun Pal <[email protected]>
Signed-off-by: Nabarun Pal <[email protected]>
520c314
to
30fe907
Compare
New changes are detected. LGTM label has been removed. |
Ummmm, this is weird. Force pushing to a branch where the PR is lgtm'ed and approved merged the PR. I think this isn't expected. Is it? |
(Although the changes proposed in the PR are not very significant) |
no, it is not expected, lgtm label was removed, how could it get merged? |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Python 3.5 was EOL'ed on 13 Sep 2020. We shouldn't support Python versions that don't get security updates anymore. (Ref 1, Ref 2)
While going through updating PyYAML due to a CVE fix (#1306), I realized that our dependencies may have dropped support for out-of-support Python minor versions. PyYAML doesn't support Python 3.5 anymore with their latest release.
If we are to fix the CVE, we need to drop Python 3.5. I think we can drop as part of releasing client version v18.y.0b1 as Python doesn't break backward compatibility within minor versions.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
None